-
-
Notifications
You must be signed in to change notification settings - Fork 14.9k
Confusing parser error #2191
Copy link
Copy link
Closed
Labels
A-diagnosticsArea: Messages for errors, warnings, and lintsArea: Messages for errors, warnings, and lintsA-parserArea: The lexing & parsing of Rust source code to an ASTArea: The lexing & parsing of Rust source code to an AST
Milestone
Metadata
Metadata
Assignees
Labels
A-diagnosticsArea: Messages for errors, warnings, and lintsArea: Messages for errors, warnings, and lintsA-parserArea: The lexing & parsing of Rust source code to an ASTArea: The lexing & parsing of Rust source code to an AST
Type
Fields
Give feedbackNo fields configured for issues without a type.
The errors says it was looking for a comma where the open paren is. I stared at at this for a long time wondering why it thought there should be a comma there. Eventually I realized that, even though it 'expected' a comma, there were other possible characters that it would have been happy with as well - in this case
<.