Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

libsyntax: Accept use foo as bar; in lieu of use bar = foo; #16468

Merged
merged 1 commit into from
Aug 14, 2014

Conversation

pcwalton
Copy link
Contributor

The old syntax will be removed after a snapshot.

RFC #47.

Issue #16461.

r? @brson

@@ -5275,6 +5275,7 @@ impl<'a> Parser<'a> {
match self.token {
token::EQ => {
// x = foo::bar
// NOTE(pcwalton, #16461): Remove after snapshot.
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Could we retain the parsing but emit a warning for awhile instead of removing this entirely after a snapshot lands? I'd just think the comment should be rephrased to say something like "make this a warning after a snapshot".

Also, could you make sure that the string "stage0" shows up here? (useful for grepping)

@alexcrichton
Copy link
Member

🌴 Thanks @pcwalton!

@alexcrichton
Copy link
Member

Ah, and one other thing, could this update the EBNF in the manual as well?

@pcwalton pcwalton changed the title libsyntax: Accept use foo as bar; in lieu of use bar as foo; libsyntax: Accept use foo as bar; in lieu of use bar = foo; Aug 14, 2014
The old syntax will be removed after a snapshot.

RFC rust-lang#47.

Issue rust-lang#16461.
bors added a commit that referenced this pull request Aug 14, 2014
The old syntax will be removed after a snapshot.

RFC #47.

Issue #16461.

r? @brson
@bors bors closed this Aug 14, 2014
@bors bors merged commit 1c16acc into rust-lang:master Aug 14, 2014
matthiaskrgr pushed a commit to matthiaskrgr/rust that referenced this pull request Feb 5, 2024
…=lnicola

minor: Recommend maintained Neovim plugin in documentation
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants