Please check the build logs for more information.
See Builds for ideas on how to fix a failed build, or Metadata for how to configure docs.rs builds.
If you believe this is docs.rs' fault, open an issue.
Opinionated Arora runtime.
Where [arora_engine] is the bare, unopinionated runtime, this crate wires
a ready-to-use [Arora]: the whole device in one object — the engine (with
the WebAssembly and native executors), the shared data store, the HAL and
bridge I/O seams, one behavior interpreter, and the step loop that drives
them. The basic behavior-tree control nodes are wired natively into
[arora_behavior_tree], so no module needs to be loaded to run a tree of
them.
Build one with the builder: pick a data store, a HAL,
zero or more bridges, the modules whose functions behaviors may call, and
the behavior interpreter — each with a sensible default, so
Arora::builder().build() yields a self-contained in-process device (fake
HAL, no bridge, an empty behavior, a private [SimpleDataStore]). Then
drive it with step (once per frame) or
run (the visible loop over step).