support unparsing of "new Object()":

tests/compiler/dart2js/unparser_test.dart

 // Copyright (c) 2012, 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.
 
 #import('dart:uri');
 #import('parser_helper.dart');
 #import("../../../lib/compiler/compiler.dart");
 #import("../../../lib/compiler/implementation/tree/tree.dart");
 
 testUnparse(String statement) {
@@ skipping 105 matching lines @@
   testDart2Dart(src, (String s) {
     Expect.equals('should_be_kept(){}main(){should_be_kept();}', s);
   });
 }
 
 testTopLevelField() {
   final src = 'final String x="asd";main(){x;}';
   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();
   testEmptyList();
   testClosure();
   testIndexedOperatorDecl();
   testNativeMethods();
   testPrefixIncrements();
   testConstModifier();
   testSimpleFileUnparse();
+  testSimpleObjectInstantiation();
   testTopLevelField();
 }