Maxwell Krohn
Maxwell Krohn
Whoops! Was reading too fast. Maybe we'll make it!
We have orthogonal issues, which is what's the default GH branch here, and what do you get when you `npm install iced-coffee-script`. Is your proposal to just change the former...
I agree about point 1, and it gives me great pains to go against it. However, I just don't know how to support monstrosities such as this: ``` coffeescript await...
thanks :( i know, i need to totally rewrite the example! On Mon, Feb 24, 2014 at 2:59 PM, Sean Robertson [email protected]: > Homepage examples fail with the following error:...
didn't even know you can do that.
Thanks for the comments @taralx . The current implementation is still attempting to treat awaited statements as expressions, but I want to kill that feature. That basket of (very hairy...
That still is an awaited expressed implementation-wise, since the while block needs to undergo a full AST rotation.
That is a great question... We probably have to reach inside and poke at the internals. Alternatively, we can trigger the overused deferral argument. It uses the same code path.
For instance: ``` iced foo = (cb) -> cb(); cb() await foo defer() ``` Outputs: ``` ICED warning: overused deferral at (undefined:3) ```
Thanks for fixing it. I had original omitted this feature since sometimes the pen-testers like to complain about "full path disclosure" in the emitted source code. That's not the thing...