relon-cap 0.1.0-rc2

Leaf crate holding Relon's canonical capability data types (CapabilityBit / NativeFnGate / Capabilities).
Documentation
  • Coverage
  • 85.11%
    40 out of 47 items documented0 out of 17 items with examples
  • Size
  • Source code size: 18.62 kB This is the summed size of all the files inside the crates.io package for this release.
  • Documentation size: 615.02 kB This is the summed size of all files generated by rustdoc for all configured targets
  • Ø build duration
  • this release: 3s Average build duration of successful builds.
  • all releases: 3s Average build duration of successful builds in releases after 2024-10-23.
  • Links
  • Homepage
  • kookyleo/relon
    0 0 0
  • crates.io
  • Dependencies
  • Versions
  • Owners
  • kookyleo

Canonical capability data types, deduplicated into a zero-dependency leaf crate.

These pure-data types were historically defined in relon-eval-api (CapabilityBit, NativeFnGate, Capabilities) and mirrored field-for-field in relon-analyzer to avoid a dependency cycle (the analyzer sits below the evaluator API in the dep graph, so it could not reach back into it). Hosting them here lets both crates depend on a single definition and re-export it at their historical public paths, so every relon_eval_api::CapabilityBit / relon_analyzer::cap::NativeFnGate reference keeps resolving while the mirror is gone.

The enforcement machinery (CapabilityGate, GatedNativeFn, NativeFnCaps) deliberately stays in relon-eval-api: it references eval-api types and is not pure data. Only the bit/grant/requirement data lives here.