Crate rearch

Modules

CapsuleHandle
The handle given to Capsules in order to Capsule::build their Capsule::Data. See CapsuleReader and SideEffectRegistrar for more.
CapsuleKey
Represents a key for a capsule. You’ll only ever need to use this directly if you are making dynamic (runtime) capsules. Most applications are just fine with static/function capsules. If you are making an incremental computation focused application, then you may need dynamic capsules.
CapsuleReader
Allows you to read the current data of capsules based on the given state of the container txn.
Container
Containers store the current data and state of the data flow graph created by capsules and their dependencies/dependents. See the README for more.
ContainerReadTxn
ContainerWriteTxn
ListenerHandle
Represents a handle onto a particular listener, as created with Container::listen().
MockCapsuleReaderBuilder
SideEffectRegistrar
Registers the given side effect and returns its build api. You can only call register once on purpose (it consumes self); to register multiple side effects, simply pass them in together! If you have an idempotent capsule that you wish to make non-idempotent, simply call register() with no arguments (or use the as_listener() side effect).

CData
Shorthand for Clone + Send + Sync + 'static, which makes returning impl Trait far easier from capsules, where Trait is often an Fn from side effects.
Capsule
Capsules are blueprints for creating some immutable data and do not actually contain any data themselves. See the documentation for more.
CapsulesWithCloneRead
A list of capsules with cloneable data. This is either a singular capsule, like foo_capsule, or a tuple, like (foo_capsule, bar_capsule).
SideEffect
Represents a side effect that can be utilized within the build function. The key observation about side effects is that they form a tree, where each side effect:
SideEffectRebuilder