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
Parser error recovery going too far #4482
Comments
Removed this from the M1 milestone. |
Removed this from the M3 milestone. |
This comment was originally written by amouravski@google.com Added Editor-AnalysisEngine label. |
Removed AnalysisEngine, Editor-AnalysisEngine labels. |
New analyzer behaves better, it marks read only place where ')' is. main() { Expected to find ';' Ideally would be great to have just one: Unexpected token ')' |
Added Analyzer-Recovery label. |
Removed Type-Defect label. |
Removed this from the Later milestone. |
Removed Oldschool-Milestone-Later label. |
Added Started label. |
https://codereview.chromium.org/785573002/ (bleeding edge revision 42136) We will now recover when there is a single unexpected token before a semicolon. Added Fixed label. |
floitsch: bad error message.
For the following line (note the extra ")" at the end of the line:
String lazyGetter = compiler.namer.isolateLazyInitializerAccess(element));
I get the following error-message (marking "String lazyGetter" red):
Multiple markers at this line
- Unexpected token 'IDENTIFIER' (expected ';')
- String is a class and cannot be used as an
expression
////////////////////////////////////////////////////////////////////////////////////
Editor: 10557
OS: Linux - amd64 (2.6.32-41-generic)
JVM: 1.6.0_24
SDK installed: true
Dartium installed: true
The text was updated successfully, but these errors were encountered: