1.9.0

[alubbe]

Hey,

I just wanted to start a quick (and hopefully short ;) ) discussion around releasing the ES6 generator & yield support into a new version of coffeescript, so that the eco-system around it (linting, syntax highlighters, etc.) can update as well. As far as I can tell this is 100% backwards-compatible and runs fine, at least on my own services.

So, what's needed for a release?

[jashkenas]

You nailed down that last big bugfix for yield, and that was the major blocker ... but there might be one or two other things floating around as well.

[alubbe]

okay so basically we are waiting. how about releasing it as a rc1 to get more adoption and thus more feedback?

[jashkenas]

We don't do "RC"s. An RC is basically just a marketing flag in the ground. The current state of master is always the RC of CoffeeScript. Anything more experimental should be on a branch.

[braco]

There's a pretty big bug that should be fixed before any new releases, IMO: #3498

The gist is that Script.createContext was not moved to vm.Script.createContext, but to vm.createContext

[mbrio]

I updated the previous conversation around vm.Script.createContext, I'll update here as well. I've created a new fork of the latest master branch of coffeescript and applied my fixes. I've created a new pull request: #3771 which contains the vm.Script.createContext bug fix.

[algesten]

io.js 1.0.0, which is released in a few weeks, have decided on V8 3.31.x. This adds quite a few ES6 features that will not be in standard nodejs. Things that may be of interest for coffeescript is block scoping (let, const), classes, octal/binary literals, symbols and template strings (follow links for list of stuff).

Has there been any discussion if some of these, if any, are to be addressed in coffeescript? If not I think we could discuss a priority order for contributions.

• The state of ES6 on io.js nodejs/node#251 (comment)
• https://github.com/seegno/io.js/wiki/The-state-of-ES6-on-io.js

[alubbe]

It kind of looks like they will be going with 3.30.x now, but the point does remain that a lot of ES6 will be available soon in regular node, not hidden behind flags. @jashkenas what is your plan for coffeescript in this future and how can we help?

[rattrayalex]

+1

CoffeeScript's lack of support for ES6, or at least a plan for support, is one of the top reasons I've heard people arguing against using it. Folks are really excited about ES6 and it'd be terrific to see, say, a CS2.0 with full ES6 spec support.

What can we do to help make this happen?

For ease of reference: https://iojs.org/es6.html
Discussion of release of 1.0.0 today: https://news.ycombinator.com/item?id=8884128

[vkbansal]

+1 for ES6 support

[vsych]

+1

[maximkoretskiy]

+1

[timaschew]

+1

[19h]

👍 Please release! We're living under the git#master bridge for over a week now.

[jashkenas]

It's a release. Thanks to @alubbe and @lydell for making this one come together.

If I missed anything important in the change log (probably), or documentation, just let me know.

[epidemian]

Great! 🎉 🍸

Thanks @lydell & Co for the hard work!

[alubbe]

Awesome, time for this http://prntscr.com/5ym952 to become semver again :)

[lydell]

About the changelog:

• https://github.com/iojs/io.js#is-it-iojs-or-iojs-or-iojs-or-iojs-or-iojs
• “Improved error reporting for string interpolation” ain’t doing justice to the lexer improvement, in my opinion. I understand if you want to keep the changelog short and simple, but something like “More robust parsing of strings and regexes—especially regarding interpolation—with improved error messages” would be more accurate.
• Perhaps something like “Several minor bug fixes” should be added as well, because lots of small ones were fixed.

[jashkenas]

Thanks.

• Fuck hipster capitalization.
• Changed to "More robust parsing and improved error messages for strings and regexes — especially with respect to interpolation."
• "Various minor bug fixes." added.

[kulicuu]

its jass
(that's a pynchon reference. i think he may have invented this hipster cap thing, or at least it was around that time )