Repository navigation
Specify admitted enum context and generated equality ABI - #488
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.
Composite equality currently specifies backend-built keys and a generated ABI with no admitted context. This spec changes the existing FR-018/interface-001 contracts to require the replay facade’s package-bound context and a generated prepared environment that retains genuine enum identities, the complete member index, and descriptor binding.
The seven existing documents preserve source/lock/full-original-package authentication, distinct admission and lookup failures, missing/wrong-environment refusal, charge-stop behavior, and record/tuple closure obligations. The remaining record/tuple owner-key capability is explicitly unresolved; enum support does not authorize a decoder or an Unsupported regression. Scalar proof execution gains no replay compilation leg.
Validation: installed Quire validation passes for all seven changed documents; diff whitespace checks pass. No Rust, Cargo, build, resolver or proof jobs ran. Behavior is PLANNED until implementation and actual native/proof qualification; this draft does not close IR-17 or IR-705.