Wrapper for multiple ImporterContextHandles

The contract of an asset handle. There are two types of asset handles: Typed -- `Handle<T>`:** When the asset's type is known when loading. Generic

Type that allows the downstream asset storage implementation to signal that an asset update operation has completed. See [`AssetStorage::update_asset`

Storage for all assets of all asset types. Consumers are expected to provide the implementation for this, as this is the bridge between [`Loader`](cr

Importers parse file formats and produce assets.

An implementation of [`HandleAllocator`] which uses an incrementing AtomicU64 internally to allocate LoadHandle IDs.

Return value for BoxedImporter::export_boxed

Trait object wrapper for [`crate::Importer`] implementations. Enables using Importers without knowing the concrete type. See [`crate::Importer`] for d

Trait object wrapper for [ImporterValue] implementations. See [ImporterValue] for documentation on fields.

A request for an asset artifact's data.

Default implementation of [`IndirectionResolver`] which resolves to the first asset in the list of candidates of the appropriate type.

Wraps the notify crate: - supports symlinks - encapsulates notify so other systems don't use it directly - generates update messages for all files on

This context can be used to maintain AssetUuid references through a serialize/deserialize cycle even if the LoadHandles produced are invalid. This is

Wrapper around lmdb with extra APIs for reading/writing capnp data and protection against too many readers/writers (will block)

Input to Importer::export

Starts a thread to watch the file system (via DirWatcher). Receives events about changes to file system and populates LMDB tables. Downstream users of