Make iced3 the default branch

[zapu]

What would be needed? What is still missing?

I link iced3 as iced and do all my iced-coffee-script using the new branch and have not encountered any issues so far. https://github.com/keybase/kbpgp builds and passes all server/browser tests without problems on iced3.

[maxtaco]

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 now?

[zapu]

I've just been wondering, because I've been using iced3 since the very first working version and never had any issues (and some obscure iced2 bugs were fixed as well because of the mainline merges). So I'm wondering what else is needed to make the iced3 "official" iced.

On the other hand, CoffeeScript has an ongoing "CS2" effort which is to modernize the code generation overall: emit ES6 classes, change to => functions (just emit ES6 => IIRC), remove arguments, probably more than that. We could either wait for it to be stable or start integrating right now, but possibly on some other, more-experimental, branch.

Nothing urgent, really, just a discussion. Maybe some other iced2/iced3 consumer will chime in.