Make definition of fragment specifier path more precise#2248
Open
fmease wants to merge 1 commit intorust-lang:masterfrom
Open
Make definition of fragment specifier path more precise#2248fmease wants to merge 1 commit intorust-lang:masterfrom
path more precise#2248fmease wants to merge 1 commit intorust-lang:masterfrom
Conversation
rustbot
added
the
S-waiting-on-review
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
2 participants
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 wording "a
TypePathstyle path" is confusing and strictly speaking meaningless since the document never defines "Rule-style" whereRuleis a grammar rule. Obviously, the original author meant "a type-style path (as defined byTypePath)". I've replaced it with "aTypePath" which is consistent with the other definitions above & below.Fixes #2219.