Repository navigation
Document current backends and guard Map allocation policies - #33
Merged
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
The code-generation guide and tutorial still described implemented LLVM/Wasm backends, collection APIs and builtin factory values as future work. Describe current targets and host requirements, label phase tables as history, and link executable examples. Factory values require concrete return types; the examples and documentation now state that boundary. The Wasm collection command uses the maintained host runner.
Add deterministic C Map capacity checks to the existing region-slack gate. Replacing 3,990 cells of a 4,000-cell list holds 65,024 bytes; restoring the old copy path grows to 134,217,216 bytes and fails the bound. One thousand small compacted maps hold 512,000 bytes; restoring the former 4 KB seed holds 4,096,000 bytes and fails the bound. Both controls must preserve the computed values. The 188-gate inventory is unchanged.
Extend the Map suffix parity fixture with a copied snapshot across compaction and replacement. Document the existing C reclamation boundary: explicit compaction may invalidate uncopied reads held on the running stack; a region result provides a durable immutable copy.
Validation:
The changes complete documentation and regression coverage for v0.1.711 after PR #32.
Completed CI at
d3d6c70c: all 17 jobs and 188 gates passed, with every gate successful exactly once in its assigned group. The Ubuntu runtime log confirms both Map old-policy controls and both C/LLVM datagram probes executed successfully.Final integration and distribution validation at
783be21c:Published as v0.1.711.