Implement new constant expressions

tests/language/language_analyzer.status

Index: tests/language/language_analyzer.status
diff --git a/tests/language/language_analyzer.status b/tests/language/language_analyzer.status
index 608454da3d04f991cc145d2312b4085a05618211..1a0747f2d74987fc77d4bf856e209cdde8a37664 100644
--- a/tests/language/language_analyzer.status
+++ b/tests/language/language_analyzer.status
@@ -170,6 +170,9 @@ regress_19413_test/01: MissingStaticWarning # Issue 19424
 # test issue 20074
 regress_20074_test: CompileTimeError # Issue 20074
 
+# The test is wrong. This is now a valid compile time constant.
+compile_time_constant_c_test/02: Fail, OK

[Paul Berry, 2014/09/18 00:05:07]

IMHO, leaving the test wrong and marking it as "Fail, OK" defeats much of the
purpose of having shared tests.  The strategy I've had luck with in past CL's
is: fix the test to agree with analyzer's (now correct) behavior.  If dart2js
and/or the VM don't have correct behavior yet, then file bugs and update their
status files to document that they don't work properly yet.

+
 # The following tests are currently assumed to be failing because the test is wrong.
 #
 application_negative_test: CompileTimeError # Test Issue 14528