wire: Separate addressless primitives from full byte-keyed trees. - #50
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
1 participant
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.
Wire previously combined addressed sending with an incomplete claim to Deixis structure. This breaking 0.3.0 revision makes Wire addressless and introduces WireTree = DeixisNode across all eight bindings, matching Bitstore Data/DataTree. Full trees expose own values, complete byte-keyed children, partial selection and decomposition; derived sending selects a node and invokes its own primitive.
Existing opaque addressed access is explicitly AddressedWire. Endpoint and return capabilities keep that interface, preserving bitwire/1 paths, invocation and ownership behavior. No opaque router is relabeled as a complete tree, and production constructors/operators remain owned by bitruntime.
Decision 0012 records the user-approved naming and supersedes the unaccepted End draft. Migration guidance, binding guides and active family docs distinguish the new contract from immutable historical evidence.
Validation: core checks and independent Go/TypeScript structural observations passed; isolated Go/npm consumers passed; Python, Rust, Swift, C++, Java and Haskell native tests and packaged consumers passed. CI separately repeats pinned historical carrier conformance. Version preparation is not registry publication; release follows an exact-commit provenance rehearsal after merge.