Live data from Hacker News

CoffeeScript 1.3.0 is out

coffeescript.org

1–10 of 55 posts

Re: CoffeeScript 1.3.0 is out

#2
For folks that are curious, we wanted to get these changes out the door -- strict mode syntax errors being a big one -- so that source maps can be the focus of the next release (probably 1.4.0).

Re: CoffeeScript 1.3.0 is out

#4
Coffeescript is quickly becoming my favorite language for one little reason: it gets out of my way and I just get things done. What more can you ask for?

My hats off to Jeremy and all the contributors. Thanks guys.

Re: CoffeeScript 1.3.0 is out

#7
Oof. Embarrassingly enough, I just bumped us to 1.3.1 -- there was an overly-strict patch that would prevent compound assignments to undeclared global variables, like this:

    global.value or= 1
... which should now compile properly as expected.

Re: CoffeeScript 1.3.0 is out

#8

Now that both ?= and or= throw errors with an undefined variable, is there another idiomatic way to write Ruby's ||= in CoffeeScript?

If you want the previous global behavior (make sure you're on 1.3.1) ... explicitly say you're making a global:

    window._ or= require "underscore"

Re: CoffeeScript 1.3.0 is out

#9

Now that both ?= and or= throw errors with an undefined variable, is there another idiomatic way to write Ruby's ||= in CoffeeScript?

If you want the previous global behavior (make sure you're on 1.3.1) ... explicitly say you're making a global: window._ or= require "underscore"

Thanks.

Re: CoffeeScript 1.3.0 is out

#10
post #5

No IcedCoffeescript's await and defer integration yet? Will we ever see them in Coffeescript's core?

First, the relevant thread:

https://github.com/jashkenas/coffee-script/pull/1942

It's not terribly likely that we'll see an IcedCoffeeScript merge soon, given that the basic needs that a merge would entail haven't been addressed. A few of them:

* We don't want to add helper libraries, like "iced.Rendevous", "icedlib.Pipeliner", or "icedlib.timeout" to our generated JS.

* Last time I checked, there was a significant slowdown even when compiling code that doesn't use "iced" features.

* For particulars on the grammar, @devongovett raises a number of worthwhile issues in the thread.

* There's still muddiness in the way that errors and exceptions are passed through the CPS transform.

* Some (important) edge cases like nested await blocks aren't handled yet, as far as I know.

... and so on.

Post reply on HN