Repository navigation
Track given membership in namespace metadata - #6287
Open
runarorama wants to merge 1 commit into
Open
runarorama wants to merge 1 commit into
runarorama wants to merge 1 commit into
Conversation
[ghstack-poisoned]
This was referenced Sep 30, 2026
This branch has not been deployed
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.
Stack from ghstack (oldest at bottom):
Add internal helpers for marking and querying dictionaries in a namespace. Marks use an opaque metadata tag and apply to all aliases of a referent in that namespace. Marking and unmarking require an existing name/referent pair and preserve unrelated metadata.
Nine focused tests pass, covering aliases, conflicted names, missing pairs, idempotence, unrelated metadata, and namespace hashing. Term/name identities remain unchanged by marking. Source declarations and commands are enabled in later stack entries; full validation is recorded in the proof files before publication.
Full validation: all 13 unit suites, 22 CLI integration tests, 391 transcripts, edit/load round trips, manual rewrites, docs HTML generation, compiled fix5507 regression, and formatting passed.