Jenny Messerly

icon location Seattle, WA icon location She's hacked on many compilers over the years (C#, VB, Python, Ruby, JS/ES6, M, Dart, to name a few). Currently works on @dart-lang's transpiler and inference.

Results 101 comments of Jenny Messerly

promote some file: references to package: self refs?

(In the meantime I'd recommend `dartanalyzer --strong` for a better UI experience)

promote some file: references to package: self refs?

Oh! you're right, we may promote analyzer warnings differently in --strong vs in dartdevc. CC @vsmenon @leafpetersen who may be looking into this. anyway happy to try taking code from...

promote some file: references to package: self refs?

Oh nice ... I wondered what "restoreUri" was for :)

promote some file: references to package: self refs?

@vsmenon and @sigmundch were looking into something like this

promote some file: references to package: self refs?

(the command line to DDC's modular compiler is quite different, but I think the issue is still there -- we don't know how to "promote" file URIs to package ones...

implement generalized tear offs

we should wait for other impls though: https://github.com/dart-lang/sdk/issues/23774

implement generalized tear offs

well, specifically, we're blocked on https://github.com/dart-lang/sdk/issues/23777 ... shouldn't be too hard to implement in our JS backend, but need analyzer support before we can even parse it

Prune stack traces

I wonder if JS has thought about this in the context of ES6 classes. Seems like it will become more common with subclassing.

js_test is broken

I think we want to support this. It's the tests for "dart:js" SDK library. But they should probably live under test/codegen/lib/ like the other SDK tests (that's where collection, convert,...

TypeScript output

good point. .d.ts files definitely would cover some of the use cases.