Crate froggy [] [src]

Component Graph System prototype.

Froggy is all about the smart component storage, unambiguously called Storage. Components inside it are automatically reference-counted, and could be referenced by a Pointer. The components are stored linearly, allowing for the efficient bulk data processing. Storage has to be locked temporarily for either read or write before any usage.

You can find more information about Component Graph System concept on the wiki. Comparing to Entity-Component Systems (ECS), CGS doesn't have the backwards relation of components to entities. Thus, it can't process all "entities" by just selecting a subsect of compoments to work on, besides not having the whole "entity" concept. However, CGS has a number of advantages:

  • you can share components naturally
  • you don't need to care about the component lifetime, it is managed automatically
  • you can have deeper hierarchies of components, with one component referencing the others
  • you can have user structures referencing components freely
  • there are no restrictions on the component types, and no need to implement any traits



Streaming iterator providing mutable components and a capability to look back/ahead.


Item of the streaming iterator.


The error type which is returned from upgrading WeakPointer.


A pointer to a component of type T. The component is guaranteed to be accessible for as long as this pointer is alive. You'd need a locked storage to access the data. The pointer also holds the storage alive and knows the index of the element to look up.


The item of ReadIter.


Iterator for reading components.


Component storage type. Manages the components and allows for efficient processing.


Weak variant of Pointer.


The item of WriteIter.


Iterator for writing components.