Support multiple resolution inputs from command line.

pkg/compiler/lib/src/resolution/members.dart

Index: pkg/compiler/lib/src/resolution/members.dart
diff --git a/pkg/compiler/lib/src/resolution/members.dart b/pkg/compiler/lib/src/resolution/members.dart
index a69b35950f82b7543c57db1a381905fd582867f6..aac37d7815d3959a45a59e1b4761606c98ce45d0 100644
--- a/pkg/compiler/lib/src/resolution/members.dart
+++ b/pkg/compiler/lib/src/resolution/members.dart
@@ -3011,7 +3011,8 @@ class ResolverVisitor extends MappingVisitor<ResolutionResult> {
     if (element is! ClassElement) return null;
     ClassElement cls = element;
     cls.ensureResolved(resolution);
-    return cls.computeType(resolution);
+    cls.computeType(resolution);
+    return cls.rawType;

[Siggi Cherem (dart-lang), 2016/05/24 18:08:15]

I'm surprised to see this change here. How is this related to the multi-file
input?

[Johnni Winther, 2016/05/25 07:54:46]

It was a latent bug. When a JS call had for instance 'JSArray' in its
spec-string, like `JS('JSArray', '[]')`, we would store the type ? +
`JSArray<E>` in the native behavior instead of `JSArray<dynamic>`.

This came up when trying to serialize 'dart:_js_helper' in another file than the
one with the JS call, since we would try to reference an external type variable
which should be possible, allowed nor supported.

   }
 
   /// Handle index operations like `a[b] = c`, `a[b] += c`, and `a[b]++`.