Uh oh!
There was an error while loading. Please reload this page.
Batch up breaking libsyntax changes - #33179
Merged
Merged
Conversation
Track the span corresponding to the `|...|` part of the closure.
…arth Track the span corresponding to the `|...|` part of the closure. lifted from rust-lang#32756 cc rust-lang#31645 libsyntax-[breaking change]
rust-highfive
commented
Apr 24, 2016
Contributor
r? @nrc (rust_highfive has picked a reviewer for you, use r? to override) |
Manishearth
commented
Apr 24, 2016
MemberAuthor
@bors r+ |
bors
commented
Apr 24, 2016
Collaborator
📌 Commit 4d746a5 has been approved by |
bors
commented
Apr 24, 2016
Collaborator
⌛ Testing commit 4d746a5 with merge 024761d... |
bors
commented
Apr 24, 2016
Collaborator
💔 Test failed - auto-win-msvc-64-cargotest |
Manishearth
commented
Apr 24, 2016
MemberAuthor
@bors p=100 |
Manishearth
commented
Apr 24, 2016
MemberAuthor
@bors retry |
tamird
commented
Apr 24, 2016
Contributor
bunch of failures in parse-fail in travis; seems legit? |
Manishearth
commented
Apr 24, 2016
MemberAuthor
investigating. |
petrochenkov
commented
Apr 24, 2016
Contributor
Manishearth
commented
Apr 24, 2016
MemberAuthor
perfect, thanks! |
Manishearth
commented
Apr 24, 2016
MemberAuthor
@bors p=0 |
Lift some restrictions on type parameters in paths Sanity check import paths for type parameters
Simplify the macro used for generation of keywords Make `Keyword::ident` private
syntax: Merge PathParsingMode::NoTypesAllowed and PathParsingMode::ImportPrefix syntax: Rename PathParsingMode and its variants to better express their purpose syntax: Remove obsolete error message about 'self lifetime syntax: Remove ALLOW_MODULE_PATHS workaround syntax/resolve: Adjust some error messages resolve: Compare unhygienic (not renamed) names with keywords::Invalid, invalid identifiers may appear to be valid after renaming
…about unexpected tokens
Paths are mostly parsed without taking whitespaces into account, e.g. `std :: vec :: Vec :: new ()` parses successfully, however, there are some special cases involving keywords `super`, `self` and `Self`. For example, `self::` is considered a path start only if there are no spaces between `self` and `::`. These restrictions probably made sense when `self` and friends weren't keywords, but now they are unnecessary. The first two commits remove this special treatment of whitespaces by removing `token::IdentStyle` entirely and therefore fixrust-lang#14109. This change also affects naked `self` and `super` (which are not tightly followed by `::`, obviously) they can now be parsed as paths, however they are still not resolved correctly in imports (cc @jseyfried, see `compile-fail/use-keyword.rs`), so rust-lang#29036 is not completely fixed. The third commit also makes `super`, `self`, `Self` and `static` keywords nominally (before this they acted as keywords for all purposes) and removes most of remaining \"special idents\". The last commit (before tests) contains some small improvements - some qualified paths with type parameters are parsed correctly, `parse_path` is not used for parsing single identifiers, imports are sanity checked for absence of type parameters - such type parameters can be generated by syntax extensions or by macros when rust-lang#10415 is fixed (~~soon!~~already!). This patch changes some pretty basic things in `libsyntax`, like `token::Token` and the keyword list, so it's a plugin-[breaking-change]. r? @eddyb
Manishearthforce-pushed
the
breaking-batch
branch
2 times, most recently
from
April 24, 2016 19:19
4968bcc to
a31658dCompareManishearth
commented
Apr 24, 2016
MemberAuthor
@bors r+ p=100 |
bors
commented
Apr 24, 2016
Collaborator
📌 Commit a31658d has been approved by |
bors
commented
Apr 24, 2016
Collaborator
bors
commented
Apr 24, 2016
Collaborator
This was referenced Apr 24, 2016
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 freeto join this conversation on GitHub.
Already have an account?
Sign in to comment
7 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.
Contains:
cc #31645