Jenny Messerly
Jenny Messerly
That's a bug in `dsend` (formerly `dinvoke`). Dynamic helpers shouldn't invoke our initializer methods. Possible quick fix: have `defineNamedConstructor` mark the method as being a named constructor, or even altogether...
Yeah, so, we were attempting to rely on the fact that static/instance/named constructor names can't conflict, at least in the same class. Similarly static member can't override instance member. ```...
@vsmenon had a related example: ``` dart class Base { Derived() => print("This shouldn't be called"); } class Derived extends Base {} main() => print(new Derived()); ``` unsure if it...
Method cascades are broken too. e.g. `..closePath()` instead of mapping to closePath it seems to map to `exports.context`
possibly we just want to make this an error, as it doesn't seem especially useful, but not sure what others think.
I wonder if it would be helpful to stage these. The things that are for SIMPLE_OPTIMIZATIONS, or for Closure's type checker, seem totally good to tackle first. I'm a bit...
by "trap" do you mean "debugger;" statement? http://www.ecma-international.org/ecma-262/6.0/#sec-debugger-statement
CC @ochafik :)
ah, yes, we don't have the code from analyzer_cli that de-dup's these. :| in general our error reporting is a bit inferior to analyzer_cli's hopefully our code goes away soon...