js: fix core.Object, output order, static const fields

lib/src/info.dart

Index: lib/src/info.dart
diff --git a/lib/src/info.dart b/lib/src/info.dart
index 80413fdad92524f3a2bd3aab992a2d3b0afc0139..60ea76c6e0dd276cd6d4de4c1d2f125e0ee5c05f 100644
--- a/lib/src/info.dart
+++ b/lib/src/info.dart
@@ -47,6 +47,18 @@ class LibraryInfo {
         name = utils.canonicalLibraryName(library);
 }
 
+class LibraryUnit {
+  final CompilationUnit library;
+  final List<CompilationUnit> parts;
+
+  LibraryUnit(this.library, this.parts);
+
+  Iterable<CompilationUnit> get units sync* {

[Jennifer Messerly, 2015/03/17 18:58:45]

=D

+    yield library;

[Jennifer Messerly, 2015/03/17 19:03:05]

on second thought... we could just reverse the order here. In other words, maybe
we should just put "parts" first in the list, and always visit that way, in
codegen and checker. WDYT?

Maybe `libraryThenParts` and `partsThenLibrary` getters? to make the distinction
obvious. that would further simplify both codegens

[Jennifer Messerly, 2015/03/17 19:11:52]

I went ahead and made both orders possible.
Kept around LibraryUnit, as it's sometimes useful to go straight to the
library's unit.

+    yield* parts;
+  }
+}
+
 // The abstract type of coercions mapping one type to another.
 // This class also exposes static builder functions which
 // check for errors and reduce redundant coercions to the identity.