support unparsing of "new Object()":

tests/compiler/dart2js/unparser_test.dart

Index: tests/compiler/dart2js/unparser_test.dart
diff --git a/tests/compiler/dart2js/unparser_test.dart b/tests/compiler/dart2js/unparser_test.dart
index 0f963acfb7bb22087d41653c94290eef004be194..523d0c96a7e6ca735a017fc2aa0810eb27b7a720 100644
--- a/tests/compiler/dart2js/unparser_test.dart
+++ b/tests/compiler/dart2js/unparser_test.dart
@@ -123,6 +123,10 @@ testTopLevelField() {
   testDart2Dart(src, (String s) => Expect.equals(src, s));
 }
 
+testSimpleObjectInstantiation() {
+  testUnparse('main(){new Object();}');

[Anton Muhin, 2012/07/09 18:31:26]

sorry, what you stopped to output now, element for Object class?

[Roman, 2012/07/10 03:20:29]

I don't think I understand the question. 

[Anton Muhin, 2012/07/10 06:56:30]

Sorry, let me rephrase it.

In the description of CL I read "support unparsing of "new Object()":", but in
CL itself I only see that you filter out corelib classes.

So I'd like to understand in details (and ideally update the description,
although it's probably too late right now), why this change helps us to unparsr
constructs like new Object?

Is it because now we shouldn't now care about elements corresponding to classes
in corelib?

On 2012/07/10 03:20:29, Roman wrote:

+}
+
 main() {
   testGenericTypes();
   testForLoop();
@@ -133,5 +137,6 @@ main() {
   testPrefixIncrements();
   testConstModifier();
   testSimpleFileUnparse();
+  testSimpleObjectInstantiation();
   testTopLevelField();
 }