Ambiguous type references require a compile time error in some special cases

tests/language/new_expression_type_args_test.dart

-// Copyright (c) 2011, the Dart project authors.  Please see the AUTHORS file
+// Copyright (c) 2012, the Dart project authors.  Please see the AUTHORS file
 // for details. All rights reserved. Use of this source code is governed by a
 // BSD-style license that can be found in the LICENSE file.
 
 // Tests showing errors using type-arguments in new expressions:
 class A<T> {
-  // Can't intantiate type parameter (within static or instance method).
-  m1() => new T();         /// 00: compile-time error
-  static m2() => new T();  /// 01: compile-time error
+  // Can't instantiate type parameter (within static or instance method).
+  m1() => new T();         /// 00: static type warning, runtime error
+  static m2() => new T();  /// 01: static type warning, runtime error
 
   // OK when used within instance method, but not in static method.
   m3() => new A<T>();
-  static m4() => new A<T>(); /// 02: compile-time error
+  static m4() => new A<T>(); /// 02: static type warning, dynamic type error
 }
 
 main() {
   A a = new A();
   a.m1(); /// 00: continued
   A.m2(); /// 01: continued
   a.m3();
   A.m4(); /// 02: continued
 }