Jenny Messerly
Jenny Messerly
fyi, I've been slowly making progress on getting Analyzer clean itself. Lots to do though
well that one's easy to fix at least ;-) Aside: ideally, they'd allow `== null` and `!= null` which is probably what we're doing. It's a nice way to express...
For interfaces, we already have some magic for dealing with some of them. Iterable comes to mind (to make it implement ES6 iterator protocol), as well as extension interfaces like...
an example of why this would help: debugging our tests using Karma, I don't get a stack trace: ``` DEBUG [web-server]: serving (cached): /Users/jmesserly/src/dev_compiler/lib/runtime/_generators.js Chrome 46.0.2457 (Mac OS X 10.10.4)...
I thought custom elements were not P1? https://github.com/dart-lang/dev_compiler/issues/521
Right now we don't have anything that would control that, but it's a good request. Definitely it should be possible to export something at module level for interop purposes. CC...
p.s. good catch & thanks for filing this!
A workaround until we fix this, might be to write a little wrapper JS module that re-exports the API you want.
related https://github.com/dart-lang/smoke/issues/8
optional args reminded me of `class Point` where folks pointed out that defaulting T to dynamic isn't very useful. So you almost want to have something more like `class Point`...