-
Notifications
You must be signed in to change notification settings - Fork 13.5k
Parser: fix ICE on failure to parse token tree #33726
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
Changes from all commits
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,15 @@ | ||
// Copyright 2016 The Rust Project Developers. See the COPYRIGHT | ||
// file at the top-level directory of this distribution and at | ||
// http://rust-lang.org/COPYRIGHT. | ||
// | ||
// Licensed under the Apache License, Version 2.0 <LICENSE-APACHE or | ||
// http://www.apache.org/licenses/LICENSE-2.0> or the MIT license | ||
// <LICENSE-MIT or http://opensource.org/licenses/MIT>, at your | ||
// option. This file may not be copied, modified, or distributed | ||
// except according to those terms. | ||
|
||
// compile-flags: -Z no-analysis | ||
|
||
macro_rules! foo { | ||
{ $+ } => () //~ ERROR: expected identifier, found `+` | ||
} //~^ ERROR: no rules expected the token `}` | ||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. If we removed the call to
I would prefer this since there's nothing wrong with the There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. You're right about the error message. I did it this way mostly because it matches the behaviour of stable rust (1.8.0). But I'm happy to change it. I have no strong feelings about which is better. Ideally I think the second error message should not be emitted at all, but that would probably be a bigger change (which I haven't looked into). There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more.
Agreed. I believe we can avoid the second error message entirely by replacing this line with self.parse_ident().unwrap_or_else(|mut e| {
e.emit();
keywords::Invalid.ident()
}) instead of modifying the |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Is there a reason we need to
bump()
here?