Throw AbstractClassInstantiationError if an abstract class is instantiated

tests/language/abstract_factory_constructor_test.dart

Index: tests/language/abstract_factory_constructor_test.dart
===================================================================
--- tests/language/abstract_factory_constructor_test.dart	(revision 11639)
+++ tests/language/abstract_factory_constructor_test.dart	(working copy)
@@ -1,28 +0,0 @@
-// 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.
-// Dart test program for constructors and initializers.
-
-// Exercises issue 2282, factory constructors in abstract classes should
-// not emit a static type warning
-
-class B extends A1 {
-  B() {}
-  method() {}
-}
-
-class A1 {
-  A1() {}
-  abstract method();
-  factory A1.make() { return new B(); }    
-}
-
-class A2 {                           
-  abstract method();                 
-  A2.make() {}
-}
-
-main() {
-  new A1.make();
-  new A2.make();              /// 01: static type warning
-}

[regis, 2012/08/31 01:16:48]

Why not turn this test into a negative one instead of deleting it?
/// 01: runtime error

[hausner, 2012/08/31 18:06:52]

We have other tests that make sure we cannot instantiate an abstract class.  But
I agree that the static type warning may still be a valuable test case.