Wrapperless dart:html and friends

lib/runtime/dart/_debugger.js

Index: lib/runtime/dart/_debugger.js
diff --git a/lib/runtime/dart/_debugger.js b/lib/runtime/dart/_debugger.js
index 481253aa67fbf3cf4cbb435b92cd129d056bb06b..2923f06b0d480c4a0aca951cba56d2d5dc6e1814 100644
--- a/lib/runtime/dart/_debugger.js
+++ b/lib/runtime/dart/_debugger.js
@@ -384,13 +384,13 @@ dart_library.library('dart/_debugger', null, /* Imports */[
     }
     preview(object) {
       let map = dart.as(object, core.Map);
-      return `${getObjectTypeName(map)} length ${map.length}`;
+      return `${getObjectTypeName(map)} length ${map[dartx.length]}`;
     }
     children(object) {
       let map = dart.as(object, core.Map);
-      let keys = map.keys[dartx.toList]();
+      let keys = map[dartx.keys][dartx.toList]();

[Jennifer Messerly, 2016/02/16 17:46:38]

how did Maps end up as a native type?
I guess some native type in dart:html implements map?

Anyway, this is kind of interesting. Our current extension method story isn't
modular/incremental. So we'll want something like @JSPeerInterface to let
interfaces declare if JS native types can implement them.

[vsm, 2016/02/18 01:13:09]

Yes, I'm pretty sure we do.
Yes!

       let entries = dart.list([], NameValuePair);
-      map.forEach(dart.fn((key, value) => {
+      map[dartx.forEach](dart.fn((key, value) => {
         let entryWrapper = new MapEntry({key: dart.as(key, core.String), value: value});
         entries[dartx.add](new NameValuePair({name: dart.toString(entries[dartx.length]), value: entryWrapper}));
       }, dart.void, [dart.dynamic, dart.dynamic]));