You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
DartBot opened this issue
Jun 27, 2012
· 1 comment
Labels
area-testCross-cutting test issues (use area- labels for specific failures; not used for package:test).P2A bug or feature request we're likely to work ontype-bugIncorrect behavior (everything from a crash to more subtle misbehavior)
kevmoo
added
P2
A bug or feature request we're likely to work on
type-bug
Incorrect behavior (everything from a crash to more subtle misbehavior)
and removed
triaged
labels
Feb 29, 2016
area-testCross-cutting test issues (use area- labels for specific failures; not used for package:test).P2A bug or feature request we're likely to work ontype-bugIncorrect behavior (everything from a crash to more subtle misbehavior)
This issue was originally filed by zundel@google.com
Case 3 expects a static type warning when a static field overrides an another static field in a superclass.
class A {
A() {} // DartC has no implicit constructors yet.
int instanceFieldInA;
static int staticFieldInA;
}
class B extends A {
B() : super() {} // DartC has no implicit constructors yet.
static int staticFieldInA; /// 03: static type warning
}
I think the test is wrong. I cannot find a place in version 0.10 of the spec where it calls for a static warning in this case.
The text was updated successfully, but these errors were encountered: