Maxwell Krohn

Yeah there are now several issues with how for loops are handled, unfortunately. On Dec 5, 2013 11:44 AM, "Chris Coyne" [email protected] wrote: > hmm, cool, I didn't even know...

Sorry David, life has been crazy with keybase.io launching and us trying to get a beta working. I haven't had any time for anything else, and for this I apologize!...

Too true! Sorry about this, for now, a workaround is `new RegExp("..")`. I'm working a bit on coffee-script now, but will eventually return to tamejs with a big rewrite. That'll...

The system is set up like it is so I can issue several releases for each release Jeremy issues in the main CoffeeScript. Is there an alternate versioning system I...

To answer your above question, you can handle errors from parallel calls as so: ``` coffeescript app.get '/', (req, res, next) -> await db.readUsersList defer e1, users db.readArticles defer e2,...

If writing control flow as library calls (i.e. async.js) is your style, then certainly there's some library-like solution for handling errors in IcedCoffeeScript that suits your needs, and is achievable...

And BTW, I think Variant #1 (`errTo` above) is doable as a clean and simple library, you just should be careful about double-calling `cb` in the case of multiple errors...

Writing of `ErrorShortCircuiter` is left to the reader, but you can look at [the Rendezvous class](https://github.com/maxtaco/coffee-script/blob/iced2/src/iced.coffee#L163-L213) for inspiration.. ``` coffeescript # Variant 1. Similar to my errTo helper readAndProcess =...

You'd plug into the standard defer-assignment-function machinery to get result1 and result2 bound to variables. Rendezvous currently does this already. Good Q about the memleak. Honestly, I don't know. I...

Here's the idea, I haven't tried it since it would require a small patch to IcedCoffeeScript. https://gist.github.com/maxtaco/5609503