Repository navigation
Use paths: qualified references follow the Rust model - #189
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.
Records the user's decision (2026-11-15): qualified references follow the Rust model, and the answers to its five questions: a namespace
usebrings in only its name; a full path works in a type position without ause; a path can go down from a name in scope; a qualified reference is frozen as its resolved path (IR, hashes and generators unchanged); a refused reference is an error at once, with a fix. Corrects the page's claim that the bare-path fix rewrites qualified references, and links core#289. Not built yet.