Jenny Messerly
Jenny Messerly
e.g. this call site: ``` js let list = []; dart.dsend(f(), 'forEach', dart.bind(list, dartx.add)); ``` Here list is just a normal array. It assets in `dart.bind` because it couldn't find...
This test uses async, but I don't think that's the issue. We desugar `++v[0]` without a return value, so the expect 42 fails. ``` dart test("suffix operator + pre-increment", ()...
[generalized tear offs](https://github.com/gbracha/generalizedTearOffs/blob/master/proposal.md) are in the 3rd edition of the [spec](https://www.dartlang.org/docs/spec/)
These might be working now if you call from Dart, but they aren't true JS functions. It would simplify things if we had them be born as JS Function objects....
We should try testing Firefox nightly & WebKit nightly & IE Edge. I tried out some basic ES6 class stuff in FF & WK nightly and it seems to work....
This has been on our radar for a while, but I don't see an issue to discuss it, so here it is. The goal would be to have a TypeScript...
it needs to be pulled over into the new test style
we immediately do this: `let ftype = dart.read(f);` .... which tries to read a symbol on null/undefined, and fails. Needs to be fixed
after https://codereview.chromium.org/1680263002/, we do two property sets in there. It is supposed to be a very fast **proto** set to handle generic extension types. I don't think an extra property...
e.g. here https://codereview.chromium.org/1969063002/diff/1/lib/src/compiler/code_generator.dart#newcode526 but also there's an "Unimplemented unknown name" message that shows up if you have a typo'd name