Remove implicit dependencies.

dart/pkg/compiler/lib/src/js_backend/backend.dart

Index: dart/pkg/compiler/lib/src/js_backend/backend.dart
diff --git a/dart/pkg/compiler/lib/src/js_backend/backend.dart b/dart/pkg/compiler/lib/src/js_backend/backend.dart
index 90ebafe724f64a76140659e1f701b2492f798b95..72570a44fad7138f2e2527570b65b866f8894959 100644
--- a/dart/pkg/compiler/lib/src/js_backend/backend.dart
+++ b/dart/pkg/compiler/lib/src/js_backend/backend.dart
@@ -949,6 +949,12 @@ class JavaScriptBackend extends Backend {
       assert(traceHelper != null);
       enqueueInResolution(traceHelper, registry);
     }
+
+    // TODO(ahe): Don't know who uses this class, but it wasn't correctly
+    // enqueued after we stopped compiling the @proxy constant eagerly.
+    world.registerInstantiatedClass(
+        interceptorsLibrary.findLocal('JSUInt31'), registry);

[ahe, 2015/02/18 16:30:56]

I have an hypothesis: the ++ and -- operators.

+
     registerCheckedModeHelpers(registry);
   }
 
@@ -2384,6 +2390,12 @@ class JavaScriptBackend extends Backend {
   }
 
   void registerMainHasArguments(Enqueuer enqueuer) {
+    // The first argument could be a list of strings.
+    enqueuer.registerInstantiatedClass(
+        listImplementation, compiler.globalDependencies);
+    enqueuer.registerInstantiatedClass(
+        stringImplementation, compiler.globalDependencies);
+
     // If the main method takes arguments, this compilation could be the target
     // of Isolate.spawnUri. Strictly speaking, that can happen also if main
     // takes no arguments, but in this case the spawned isolate can't