improve error message when incorrectly using cascades #10332
Assignees
Labels
analyzer-recovery
area-analyzer
Use area-analyzer for Dart analyzer issues, including the analysis server and code completion.
type-enhancement
A request for a change that isn't a bug
Comments
|
I hope to get to recovery before M5, but can't make any promises. Set owner to @bwilkerson. |
|
Added Analyzer-Recovery label. |
|
Removed this from the Later milestone. |
|
Removed Oldschool-Milestone-Later label. |
|
I'm not sure when this changed, but we now produce "Expected an identifier". It's not ideal in this case (you'd kind of like "Extra semicolon"), but it does have advantages for code completion, which might outweigh the disadvantages. At least there's only one error message. Added Fixed label. |
sigmundch
added
Type-Enhancement
area-analyzer
kevmoo
added
type-enhancement
This issue was closed.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Consider this program that uses cascades, but that has an error (there is an extra ';' after add(1)):
main() {
var n = [];
n..add(1);
..add(2);
}
The new analyzer gives a warning. It took me a while to figure out what was wrong in that line of code:
[warning] Undefined name '' (warning.dart:4:5)
The old analyzer used to say:
file:.../warning.dart:4:4: Unexpected token '..'
3: n..add(1);
4: ..add(2);
~~
file:.../warning.dart:4:6: Unexpected token 'IDENTIFIER' (expected ';')
3: n..add(1);
4: ..add(2);
~~~
Compilation failed with 2 problems.
The text was updated successfully, but these errors were encountered: