Enum RuntimeCrateSource 

pub enum RuntimeCrateSource {
    Workspace,
    Registry {
        version: String,
    },
}

How a generated project resolves the logicaffeine runtime crates.

Inside the monorepo we stage the crate sources beside the generated program and path-depend on them (hackable, offline). An installed largo has no checkout to stage from, so it version-depends on the published crates.io releases pinned to this compiler’s OWN version — the generated Rust and the runtime API can then never drift.

Variants

Workspace

Monorepo checkout: stage sources under ./crates and path-depend.

Registry

Standalone install: depend on the crates.io releases at version.

Fields

version: String

Implementations

impl RuntimeCrateSource

pub fn detect() -> Self

A monorepo checkout stages sources; anywhere else (an installed largo) pulls the matching crates.io release at this compiler’s own version.

pub fn is_workspace(&self) -> bool

True inside a checkout (stage sources + path-depend); false for an installed largo (nothing to copy — depend on crates.io).

pub fn data_dep(&self) -> String

The logicaffeine-data dependency line for this source.

pub fn system_dep(&self, features: &[&str]) -> String

The logicaffeine-system dependency line carrying features.

pub fn linux_engine_section(&self) -> String

The target section every generated project ends its dependencies with: on Linux the runtime carries io-uring, which cargo unifies with the features its [dependencies] line names, so a compiled server has the thread-per-core io_uring engine and the UringVfs, and every other target builds without them.