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

tests/language/language.status

Index: tests/language/language.status
diff --git a/tests/language/language.status b/tests/language/language.status
index ca90a14723a21ae7ecc62d83ad81b25aee4fd865..d1dde4d04712883874c1e51819dc2eb496aa0510 100644
--- a/tests/language/language.status
+++ b/tests/language/language.status
@@ -44,6 +44,7 @@ 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
@@ -93,6 +94,7 @@ 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.