docs.rs failed to build fp-runtime-0.5.0
Please check the build logs for more information.
See Builds for ideas on how to fix a failed build, or Metadata for how to configure docs.rs builds.
If you believe this is docs.rs' fault, open an issue.
Please check the build logs for more information.
See Builds for ideas on how to fix a failed build, or Metadata for how to configure docs.rs builds.
If you believe this is docs.rs' fault, open an issue.
Visit the last successful build:
fp-runtime-0.2.0
fp-runtime
Runtime policies, evidence ledgers, and asupersync interop for the frankenpandas execution layer.
Part of the frankenpandas workspace.
When to depend on fp-runtime directly
Most users should depend on the umbrella frankenpandas crate
instead. Direct dependency makes sense when:
- Building a frankenpandas-compatible execution harness that needs policy control over alignment / coercion / error handling.
- Interoperating with the asupersync concurrency system (enable the
asupersyncCargo feature).
Key types
RuntimePolicy— strict / hardened / lenient mode selection for DataFrame / Series operations. Controls when dtype promotion errors vs silently coerces.EvidenceLedger— structured audit trail for every alignment decision. Useful for debugging / replay.
Features
asupersync— enablesasupersync::Outcome<T, E>interop for cancellable / panicking operations. Requires asupersync as a runtime dep.
Status
Stable. Pinned to asupersync 0.5.0 (verified in docs/planning/UPGRADE_LOG.md).