Files
alknet/docs/architecture/questions/070-no-std-alloc-support.md
T
deepseek-v4-pro 01cc3a0367 docs(typedef): clarify OQ-070 WASM vs no_std distinction
WASM (wasm32-unknown-unknown) has std via wasm-bindgen and is not
blocked by this OQ. The crate is WASM-clean by construction. This OQ
is about bare-metal embedded targets only.
2026-07-21 08:05:24 +00:00

23 lines
1.2 KiB
Markdown

# OQ-070: `no_std` + `alloc` support
- **Origin**: [crates/typedef/overview.md](crates/typedef/overview.md);
`docs/research/alknet-typedef/findings.md` §"Open Questions" (OQ 6)
- **Status**: deferred(scope)
- **Door type**: Two-way (additive — can be added as a feature gate
without changing the existing `std` API)
- **Priority**: low
- **Impacts**: Blocks bare-metal embedded targets (microcontrollers
running Rust without `std`). Does NOT block any current deployment
target. Does NOT block WASM — `wasm32-unknown-unknown` has `std`
available via `wasm-bindgen`; the crate is WASM-clean by construction
(no tokio, no platform deps, `jsonschema` builds for WASM with
`default-features = false`).
- **Blocked on**: An embedded use case that requires `no_std` + `alloc`
(e.g., a microcontroller running Rust without `std`).
- **Resolution**: Not yet decidable. Target `std` for v1. If embedded
use cases emerge, `no_std` + `alloc` can be added as a feature gate
later. The engine's core (offset computation, read/write) is already
allocation-free — it operates on `&[u8]` slices. The `jsonschema`
dependency is the only `alloc` consumer.
- **Cross-references**: ADR-095