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
language/constructor_negative_test #11586
Comments
cc @peter-ahe-google. |
Proposed change to multi-test in https://codereview.chromium.org/23403007/. |
Removed this from the 1.6 milestone. |
Removed Oldschool-Milestone-1.6 label. |
scheglov
added
Type-Defect
area-test
Cross-cutting test issues (use area- labels for specific failures; not used for package:test).
labels
Aug 4, 2014
kevmoo
added
type-bug
Incorrect behavior (everything from a crash to more subtle misbehavior)
and removed
priority-unassigned
labels
Feb 29, 2016
This has already been fixed for Dart 1.0 and is perfectly valid for Dart 2.0 (optional new). |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Missing "new" or "const" looks as function invocation, so is warning.
So, this test is not negative.
12.14.3 Unqualied Invocation
Otherwise, i is equivalent to this:id(a1; : : : ; an; xn+1 : an+1; : : : ; xn+k : an+k).
12.15.1 Ordinary Invocation
Let T be the static type of o. It is a static type warning if T does not have
an accessible (3.2) instance member named m. If T:m exists, it is a static type
warning if the type F of T:m may not be assigned to a function type.
The text was updated successfully, but these errors were encountered: