fix some tests

tests/language/src/OverrideMethodWithFieldTest.dart

Index: tests/language/src/OverrideMethodWithFieldTest.dart
diff --git a/tests/language/src/OverrideMethodWithFieldTest.dart b/tests/language/src/OverrideMethodWithFieldTest.dart
index 72a2847598e802db5c69d9d9b77557e2af8b7a81..d4128b0434c2e6b824316fa1b476f65621370fe7 100644
--- a/tests/language/src/OverrideMethodWithFieldTest.dart
+++ b/tests/language/src/OverrideMethodWithFieldTest.dart
@@ -22,6 +22,7 @@ main() {
   var s = new Sub();
   Super sup = s;
   Sub sub = s;
+  print(s.instanceMethod);

[jimhug, 2011/10/31 23:36:31]

This instanceMethod field overriding the super method is not necessarily an
error until it is referred to.

[ngeoffray, 2011/11/01 08:17:34]

Because you've allocated a Sub, I'm not sure here. Shouldn't we analyze the
class at the point an instance is allocated?

[jimhug, 2011/11/01 15:07:11]

That's the key question here.  When I allocate a Sub do I have to verify that
all of its members are correctly defined, or am I allowed to wait until the
first reference of such a member to perform the checks.  I would be happiest if
we could adopt that rule in order to allow the compiler to do the minimum amount
of work truly required to make a given program run.  I would then like to have
--compile_all be the flag that can force all of these checks to be done if the
programmer would prefer.

On 2011/11/01 08:17:34, ngeoffray wrote:

   Expect.equals(42, s.superInstanceMethod());
   Expect.equals(42, sup.superInstanceMethod()); // Intentional static type error.
   Expect.equals(42, sub.superInstanceMethod());