zcomponents 0.2.0

ZComponents is a stupid component storage
Documentation
  • Coverage
  • 42.86%
    6 out of 14 items documented1 out of 13 items with examples
  • Size
  • Source code size: 20.93 kB This is the summed size of all the files inside the crates.io package for this release.
  • Documentation size: 2.56 MB This is the summed size of all files generated by rustdoc for all configured targets
  • Links
  • Homepage
  • ozkriff/zemeroth
    1438 92 84
  • crates.io
  • Dependencies
  • Versions
  • Owners
  • ozkriff

ZComponents - a stupid component storage

Crates.io Docs.rs

I find "serious" ECS to be an overkill for turn-based game logic, so I've created this simple library that does only one thing: stores your components.

Basic Example

use zcomponents::zcomponents_storage;

#[derive(PartialEq, Eq, Clone, Copy, Debug, Hash, Default)]
pub struct Id(i32);

#[derive(Clone, Debug)]
pub struct SomeComponent(pub i32);

#[derive(Clone, Debug)]
pub struct SomeFlag;

zcomponents_storage!(Storage<Id>: {
    component: SomeComponent,
    flag: SomeFlag,
});

let mut storage = Storage::new();

let id0 = storage.alloc_id();
storage.component.insert(id0, SomeComponent(0));

let id1 = storage.alloc_id();
storage.component.insert(id1, SomeComponent(1));
storage.flag.insert(id1, SomeFlag);

storage.component.get_mut(id0).0 += 1;

if let Some(component) = storage.component.get_opt_mut(id1) {
    component.0 += 1;
}

storage.flag.remove(id1);

storage.remove(id0);

See a more advanced example in crate's documentation.

Implementation

It's implemented as a simple macro and a bunch of naive HashMaps so don't expect any outstanding performance.