Support for dart:typed_data

tool/input_sdk/private/operations.dart

Index: tool/input_sdk/private/operations.dart
diff --git a/tool/input_sdk/private/operations.dart b/tool/input_sdk/private/operations.dart
index a79fc5bea998bc37c57deb7f6a4a0b9282eaad1a..dcac6ff47eb4f0dfd201a17b0b965e3332a74f37 100644
--- a/tool/input_sdk/private/operations.dart
+++ b/tool/input_sdk/private/operations.dart
@@ -165,7 +165,8 @@ _ignoreTypeFailure(actual, type) => JS('', '''(() => {
 
 strongInstanceOf(obj, type, ignoreFromWhiteList) => JS('', '''(() => {
   let actual = $realRuntimeType($obj);
-  if ($isSubtype(actual, $type) || actual == $jsobject) return true;
+  if ($isSubtype(actual, $type) || actual == $jsobject ||
+      actual == $int && type == $double) return true;

[Jennifer Messerly, 2016/02/10 00:20:30]

should we put this logic in isSubtype?

at runtime we have no way of distinguishing between doubles and ints. For
example, if I have a List<double> it may contain ints too:

var list = <double>[1.0, 1.5, 2.0];
print(list.runtimeType); // List<double>
print(list[0].runtimeType); // int
print(list[1].runtimeType); // double
print(list[2].runtimeType); // int

Feels like it'd be more consistent to allow `int <: double` subtyping at
runtime.

Otherwise I think there are places we might call subtype instead of
strongInstanceOf and get the wrong result...

[vsm, 2016/02/11 22:36:06]

I thought about doing that, but it's a bigger change.  E.g.,: this throws (in
checked mode) today on the VM and dart2js:

void main() {
  List l1 = <int>[1, 2];

  List<double> l2 = l1;
  print(l2);
}

I do agree that it's more consistent though with how we (and dart2js) treat
numbers.

   if ($ignoreFromWhiteList == void 0) return false;
   if ($isGroundType($type)) return false;
   if ($_ignoreTypeFailure(actual, $type)) return true;