DartVM: no compile-time error for wrong interface methods overriding

[DartBot]

This issue was originally filed by ief...@unipro.ru

---

What steps will reproduce the problem?
consider the following test:
interface I {
  void m1();
}

interface J extends I {
  void m1(int i);
}

main() {
  J j = null;
  try {j.m1(null);} catch (var e) {}
}

What is the expected output? What do you see instead?
Expected: compile-time error
Actual: successful completion

What version of the product are you using? On what operating system?
DartVM r2810

Please provide any additional information below.
co19 tests:
LangSpecTest/08_Interfaces/1/Methods/A03/t01
LangSpecTest/08_Interfaces/1/Methods/A03/t02
LangSpecTest/08_Interfaces/1/Methods/A03/t03
LangSpecTest/08_Interfaces/1/Methods/A03/t04
LangSpecTest/08_Interfaces/1/Methods/A04/t01
LangSpecTest/08_Interfaces/1/Methods/A04/t02
LangSpecTest/08_Interfaces/1/Methods/A04/t03
LangSpecTest/08_Interfaces/1/Methods/A04/t04
LangSpecTest/08_Interfaces/1/Methods/A04/t05

[dgrove]

Added Area-VM, Triaged labels.

[iposva-google]

Marked this as being blocked by #1031.

[iposva-google]

Matthias, can you please work with Gilad to resolve whether these are still expected to be compile-time errors and whether they should be. See the blocking bug.

---

cc @gbracha.
Set owner to @mhausner.
Added Accepted label.

[gbracha]

Changing this is under debate, but my current expectation is that it will not change.

[peter-ahe-google]

FYI: dart2js complains about most of these cases. However, dart2js only validates members of instantiated classes and their supertypes. This means that the example in the first comment will not be rejected (unless a --compile-all option is added to dart2js).

---

Marked this as being blocked by #1031.
Unmarked this as being blocked by #1031.

[iposva-google]

The example in the original report works fine now.

---

Added Fixed label.