about summary refs log tree commit diff
path: root/src/libsyntax/ext
diff options
context:
space:
mode:
authorbors <bors@rust-lang.org>2016-11-11 02:51:01 -0800
committerGitHub <noreply@github.com>2016-11-11 02:51:01 -0800
commit4da129d98419733bb408141ca53610bb77368cf0 (patch)
tree1355601d6d0ff942eef9ca2c4ee27e6913bca9a1 /src/libsyntax/ext
parent280362a02df97670dd08ed19557c81b504b395c3 (diff)
parenteed86fac91c12707b8ef6693a5cf2106ca6652c0 (diff)
downloadrust-4da129d98419733bb408141ca53610bb77368cf0.tar.gz
rust-4da129d98419733bb408141ca53610bb77368cf0.zip
Auto merge of #37246 - goffrie:no-loop, r=jseyfried
Don't spin expanding stmt macros.

If we can't make progress when parsing a macro expansion as a statement then we should just bail.

This alleviates the symptoms shown in e.g. #37113 and #37234 but it doesn't fix the problem that parsing invalid enum bodies (and others) leaves the parser in a crappy state.

I'm not sold on this strategy (checking `tokens_consumed`), so if anyone has a better idea, I'm all ears!
Diffstat (limited to 'src/libsyntax/ext')
-rw-r--r--src/libsyntax/ext/expand.rs4
1 files changed, 3 insertions, 1 deletions
diff --git a/src/libsyntax/ext/expand.rs b/src/libsyntax/ext/expand.rs
index e3b23e239f9..c3608aac0b4 100644
--- a/src/libsyntax/ext/expand.rs
+++ b/src/libsyntax/ext/expand.rs
@@ -533,7 +533,9 @@ impl<'a> Parser<'a> {
             }
             ExpansionKind::Stmts => {
                 let mut stmts = SmallVector::zero();
-                while self.token != token::Eof {
+                while self.token != token::Eof &&
+                      // won't make progress on a `}`
+                      self.token != token::CloseDelim(token::Brace) {
                     if let Some(stmt) = self.parse_full_stmt(macro_legacy_warnings)? {
                         stmts.push(stmt);
                     }