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
Dart2js and dart2dart wrongly report compile-time error for non conflicting constructor and setter names #13639
Comments
Added this to the M7 milestone. |
Removed this from the 1.6 milestone. |
Removed Oldschool-Milestone-1.6 label. |
There is also a conflict between methods and setter in setter4_test |
Dart 2.0 (Analyzer) now reports compile-time error. |
I'm not aware of any changes in this regard for Dart 2.0, so are we sure it's correct for the analyzer to report a compile-time error? |
this appears now to be working correctly - bad_constructor_test is not mentioned in any .status file at at this time. |
(except for the Dart1 implementation of dart2js) |
Spec:
The name of a setter is obtained by appending the string `=' to the identifier given in its signature.
Hence, a setter name can never conflict with, override or be overridden by a getter or method.
bad_constructor_test/05 wrongly reports a compile-time error
The text was updated successfully, but these errors were encountered: