Properly register types on the JS foreign instruction.

sdk/lib/_internal/compiler/implementation/native_handler.dart

Index: sdk/lib/_internal/compiler/implementation/native_handler.dart
===================================================================
--- sdk/lib/_internal/compiler/implementation/native_handler.dart	(revision 17700)
+++ sdk/lib/_internal/compiler/implementation/native_handler.dart	(working copy)
@@ -539,13 +539,22 @@
         return behavior;
       }
       var behavior = new NativeBehavior();
+      LinkBuilder<Element> types = new LinkBuilder<Element>();

[ahe, 2013/01/28 15:14:31]

This looks like a list of "elements", not "types".

       for (final typeString in specString.split('|')) {
         var type = _parseType(typeString, compiler,
             (name) => resolver.resolveTypeFromString(name),
             jsCall);
         behavior.typesInstantiated.add(type);
         behavior.typesReturned.add(type);
+        if (type == SpecialType.JsObject) {
+          types.addLast(compiler.objectClass);
+        } else if (type == SpecialType.JsArray) {
+          types.addLast(compiler.backend.listImplementation);
+        } else {
+          types.addLast(type.element);
+        }
       }
+      compiler.typesTask.typedNodes[jsCall] = types.toLink();

[ahe, 2013/01/28 15:14:31]

Please abstract this operation.

[sra1, 2013/01/28 20:12:20]

Move the assignment out to the call site of ofJsCall or to the ssa builder.

NativeBehavior is just data about the operation.
I'd like to keep the NativeBehavior methods idempotent.
We will add data for use by effect analysis, global type inference, range
analysis etc to NativeBehavior.
Adding updates to other compiler phases here will rapidly get ugly as more
phases become clients of the information. 

Calling NativeBehavior.ofJsCall should not have any side-effects.
For example, the ssa builder should be able to call NativeBehavior.ofXXX rather
than rely on some other phase caching the derived information.
It will rapidly get ugly when we also need the types for global type analysis,
and the effects (when we add those.).

It would be OK to cache the NativeBehavior.

Converting from NativeBehavior to HType should be a separate operation and made
to work on NativeBehavior.NONE (returned in another branch.)
Then the same code can be used at calls to native methods to get the returned
type, which will help with the DOM benchmarks.

       return behavior;
     }
 
@@ -880,8 +889,7 @@
     }
 
     DartString jsCode = new DartString.literal(nativeMethodCall);
-    builder.push(
-        new HForeign(jsCode, const LiteralDartString('Object'), inputs));
+    builder.push(new HForeign(jsCode, HType.UNKNOWN, inputs));
     builder.close(new HReturn(builder.pop())).addSuccessor(builder.graph.exit);
   } else {
     if (parameters.parameterCount != 0) {