Skip to main content

Crate concinnity_host

Crate concinnity_host 

Source
Expand description

concinnity-host: what the engine needs from the machine it runs on.

Three charters, sharing nothing but that dependency:

  • store: the project’s state tree on disk, and the reads over it.
  • thread: the worker pool and the per-thread interner.
  • scratch: the temporary paths an external tool is handed.

They stay separate all the way down. Nothing in store reaches into thread, and nothing in thread names a path. scratch names paths no project owns, which is why it is not part of store.

Modules§

scratch
Scratch paths in the machine’s temporary directory.
store
The project’s state tree on disk: where it is anchored (paths), how a source asset is found inside it (source), how the compiled blob is read out of it (blob), how the runtime’s regenerable artifacts are kept in it (cache), and how a regenerable container is published without a reader ever seeing it part-written (atomic).
thread
The thread-scoped services the rest of the engine builds on, kept out of the vocabulary and compute layer below them (concinnity-core) so that layer needs no operating system.