Chromium Code Reviews
chromiumcodereview-hr@appspot.gserviceaccount.com (chromiumcodereview-hr) | Please choose your nickname with Settings | Help | Chromium Project | Gerrit Changes | Sign out
(1417)

Unified Diff: runtime/vm/parser.cc

Issue 11027036: Better error message for const loop variables (Closed) Base URL: http://dart.googlecode.com/svn/branches/bleeding_edge/dart/
Patch Set: Created 8 years, 2 months ago
Use n/p to move between diff chunks; N/P to move between comments. Draft comments are only viewable by you.
Jump to:
View side-by-side diff with in-line comments
Download patch
« no previous file with comments | « no previous file | no next file » | no next file with comments »
Expand Comments ('e') | Collapse Comments ('c') | Show Comments Hide Comments ('s')
Index: runtime/vm/parser.cc
===================================================================
--- runtime/vm/parser.cc (revision 13240)
+++ runtime/vm/parser.cc (working copy)
@@ -5268,7 +5268,12 @@
bool Parser::IsForInStatement() {
const intptr_t saved_pos = TokenPos();
bool result = false;
- if (CurrentToken() == Token::kVAR || CurrentToken() == Token::kFINAL) {
+ // Allow const modifier as well when recognizing a for-in statement
+ // pattern. We will get an error later if the loop variable is
+ // declared with const.
+ if (CurrentToken() == Token::kVAR ||
+ CurrentToken() == Token::kFINAL ||
+ CurrentToken() == Token::kCONST) {
ConsumeToken();
}
if (IsIdentifier()) {
« no previous file with comments | « no previous file | no next file » | no next file with comments »

Powered by Google App Engine
This is Rietveld 408576698