Expand description
§nwnrs-resmemfile
In-memory nwnrs-resman::ResContainer implementation.
§Why This Crate Exists
Downloaded or synthetically generated payloads need to enter the resource
lookup chain without touching the filesystem. Without an in-memory container,
callers would need to write bytes to a temporary file just to create a
ResFile. This crate lets any byte buffer participate in a ResMan lookup
chain directly.
§Scope
- wrap a byte buffer as a single resource entry
- expose synthetic or downloaded payloads through the same container interface as on-disk resources
§See also
nwnrs-resman, which defines theResContainerabstraction this crate implementsnwnrs-resfile, the on-disk equivalent for single-file resources
Modules§
- prelude
- Common imports for consumers of this crate.
Structs§
- ResMem
File - An in-memory resource exposed as a one-entry resource container.
Enums§
- ResMem
File Error - Errors returned while building an in-memory resource container.
Functions§
- read_
resmemfile - Wraps owned bytes as a one-entry in-memory resource container.
- read_
resmemfile_ arc - Wraps shared bytes as a one-entry in-memory resource container.
Type Aliases§
- ResMem
File Result - Result type for in-memory resource operations.