Remove now unnecessary suppressions.

tests/language/language.status

Index: tests/language/language.status
diff --git a/tests/language/language.status b/tests/language/language.status
index 47faf4542fb8ae5331ed87694e66404de30ab6be..bc4fc91eb589859d0ec7797c20caae74c7bd74de 100644
--- a/tests/language/language.status
+++ b/tests/language/language.status
@@ -185,9 +185,6 @@ pseudo_kw_illegal_test/16: Fail
 pseudo_kw_test: Fail
 # external keyword is not yet supported by dart2js/dart2dart.
 external_test/*: Skip
-# Final top-level field declarations without initializer do not lead to errors in dart2js frontend.

[ahe, 2012/08/21 15:55:18]

Hmm. I think the Dart VM is handling this error for you.

[Anton Muhin, 2012/08/21 18:27:30]

Before your change, F1/F3 were not even analyzed as they are never used.  Hence
dart2dart didn't emit it back for DartVM to complain about them.

[ahe, 2012/08/21 18:54:21]

I know. I just think it is unfortunate that dart2dart passes a test that it
should fail because the VM saves. Short-term, this is fine, but long term you
want to make sure that dart2dart doesn't spit out garbage. 

Hopefully, this should come for free as dart2js implements all semantic checks. 

-final_syntax_test/03: Fail
-final_syntax_test/04: Fail
 # Call operator is not supported by DartVM (see suppression above.)
 call_operator_test: Fail
 # dart2js frontend doesn't even analyse problematic classes.