SuperNegativeTest doesn't match current spec

[DartBot]

This issue was originally filed by jimhug@google.com

---

It looks like all three implementations (dartc, vm and frog) currently fail on this test, and the spec says:
  "If no superinitializer is provided, an implicit superinitializer of the form super() is added at the end of k’s initializer list, unless the enclosing class is class Object."

This was reported as Bug 4400118, but I wanted to get this into the public system and hopefully get this resolved quickly as an obvious test bug. I don't know if there is a test for the correct insertion of the missing super call - but this test could be usefully converted to do that with a little extra verification that A's constructor is actually called when creating a new B.

[DartBot]

This comment was originally written by drfibonacci@google.com

---

Added Area-Frog, Triaged labels.

[DartBot]

This comment was originally written by @mhausner

---

SuperNegativeTest is indeed obsolete. Dart specifies that an implicit call to super() is added to the initializer list if no explicit super call is present.

We have Constructor4Test to check that implicit super calls are added, so I think the best is to eliminate SuperNegativeTest. I'll do that.

---

Set owner to @mhausner.

[DartBot]

This comment was originally written by @mhausner

---

Test removed.

---

Added Fixed label.