frog: check that const constructors have potentially const initializers. Also

tests/language/language.status

 # Copyright (c) 2011, 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.
 
 # This directory contains tests that are intended to show the
 # current state of the language.
 
 # In order to maintain maximum test coverage for all builds,
 # please use the following procedure to mark a test
 # failed on architectures other than the one you are working on.
@@ skipping 26 matching lines @@
 ImplicitThisTest/none: Fail # Issue 374
 
 LibrarySameNameUsedTest: Fail    # Issue 686
 
 # These bugs refer currently ongoing language discussions.
 Constructor5Test: Fail          # (Discussion ongoing)
 Constructor6Test: Fail          # (Discussion ongoing)
 
 # Regular bugs which should be fixed.
 
+ConstInit6NegativeTest: Fail       # Issue 811
 WrongNumberTypeArgumentsTest: Fail # Issue 441
 
 # DartC or Frog specific tests that should not be run by the VM
 *DartcTest: Skip
 *DartcNegativeTest: Skip
 *FrogTest: Skip
 *FrogNegativeTest: Skip
 
 
 [ $component == vm && $mode == debug ]
@@ skipping 29 matching lines @@
 BlackListedTest/09: Fail # Bug 5469684
 BlackListedTest/10: Fail # Bug 5469684
 BlackListedTest/11: Fail # Bug 5469684
 BlackListedTest/12: Fail # Bug 5469684
 BlackListedTest/13: Fail # Bug 5469684
 BlackListedTest/14: Fail # Bug 5469684
 CTConstTest: Fail            # Bug 4510015.
 CallThroughNullGetterTest: Fail # Throw ObjectNotClosure instead of NullPointerException.
 CharEscapeTest: Fail
 ClassOverrideNegativeTest: Fail  # Bug 4205768.
+ConstInit5NegativeTest: Pass  # Should fail at compile-time, not at runtime

[Siggi Cherem (dart-lang), 2011/12/12 18:04:38]

We should go through negative tests and try to see if we can make them "pass"
when the feature is not implemented. In this example, the code also has a
runtime assertion that is not necessary and that it is hiding the real issue.

[jimhug, 2011/12/12 18:14:30]

SGTM - I'd also like to figure out how to ensure that the negative tests are
reporting errors on the correct lines - as an opt-in feature to not break the
VM.

On 2011/12/12 18:04:38, sigmund wrote:

 DefaultFactoryLibraryTest: Fail          # Issue 514
 ConstObjectsAreImmutableTest: Fail  # Bug 5202940
 Constructor2NegativeTest: Fail  # Bug 4208594.
 Constructor2Test: Fail       # Issue 255
 Constructor3Test: Fail       # Issue 257
 Constructor4Test: Fail       # Issue 286
 Constructor5Test: Fail       # Issue 8440015 + 'super' initializer does not parse
 Constructor6Test: Fail       # Issue 8440015 + 'super' initializer does not parse
 DivByZeroTest: Fail          # Bug 5184183
 DynamicTest: Fail            # Bug 5527899.
@@ skipping 238 matching lines @@
 StaticField2RunNegativeTest: Fail
 
 [ $arch == x64 ]
 *: Skip
 
 [ $arch == simarm ]
 *: Skip
 
 [ $arch == arm ]
 *: Skip