Would IcedCS ever be merged into Coffeescript?

[iamwilhelm]

I didn't see this info anywhere, and was just wondering if IcedCoffeeScript would ever be merged into Coffeescript. I'd want to use ICS in production, but I'm afraid it diverging from CoffeeScript, or not regularly being mirrored with CoffeeScript's updates. Can @maxtaco or anyone else that is using ICS regularly speak to this? Thanks.

[maxtaco]

I have been pretty good about keeping ICS merged with the main line. I believe it is largely up-to-date. I haven't started working on coffee-script redux yet. That will likely be a full reimplementation. And I don't think there are any plans to merge iced with the mainline, sadly. I wish they had been more receptive to the idea but unfortunately they weren't. @malgorithms and I still use ICS for all of our projects so I plan to work on it indefinitely.

[iamwilhelm]

What was the reason the CS team didn't want to merge it? Did it not coincide with their intended goal and purpose with Coffeescript?

[maxtaco]

See jashkenas#1942

[iamwilhelm]

Cool, thanks for the update. I think my hesitation in adopting it was just what I mentioned: being stuck in a version of coffeescript that won't get updated. I think if the documentation was updated to reflect what you just told me, as well as the Changelog being updated to being as close as possible to the latest Coffeescript version, that'd give me some confidence as a newcomer to iced coffee script. Thanks for the info!

[iamwilhelm]

One last thing. Can you use iced as a required module inside a coffeescript program? Or do you need the ics compiler to run it?

[maxtaco]

Iced is a pretty major change to the coffee compiler. It makes some deep changes in the way code is emitted from the compiler to implement the CPS transform. So it can't work as a module.

[ranska]

And what about ported iced to livescript ?
livescript team look more open for thing's who change strongly from pur js.

[vendethiel]

And what about ported iced to livescript ?

I strongly believe this is something a library should do, and we have several tools for that already (i.e. backcalls)