Permalink

Comparing changes

Choose two branches to see what’s changed or to start a new pull request. If you need to, you can also .

Open a pull request

Create a new pull request by comparing changes across two branches. If you need to, you can also .
...
Commits on May 21, 2015
@ide ide Replace "instanceof Array" in transformer with "[object Array]" compa…
…rison

Testing with `'[object Array]' is Object::toString.call element` allows arrays from another JS context to be properly handled. The specific use case here is to support jest, which sets up JS contexts using Node/io.js's "vm" module. This approach works in ES3 environments in contrast with ES5's `Array.isArray`.
2087923
Commits on May 27, 2015
@jashkenas correct release date e339f5f
Commits on Jun 05, 2015
@michaelficarra michaelficarra Merge pull request #3985 from ide/array-check
Replace "instanceof Array" in transformer with "[object Array]" comparison
1f197fc
Commits on Jun 22, 2015
@rvagg rvagg don't copy arguments or caller from require
causes an error in io.js where strict-mode is set on internal modules

Fixes: #3810
75ae45e
@michaelficarra michaelficarra Merge pull request #4019 from rvagg/master
Don't copy arguments or caller from require
342b395
Commits on Jul 08, 2015
@yjerem yjerem Reset @seenFor in lexer before tokenizing 3d7d68a
@michaelficarra michaelficarra Merge pull request #4029 from yjerem/reset-seenfor
Reset @seenFor in lexer before tokenizing
2d1a6fa
Commits on Aug 16, 2015
Bruno Bernardino Closes #4036: "Try catch" optimisation
Let me know if there's something I should be doing differently as this is my first contribution to coffeescript.
I fixed the reported issue where a generated variable could clash with a user-defined one in a try/catch block.
I added a test for a few scenarios with different variable names for a try/catch, to confirm the fix and avoid regressions.
24e8f1c
Bruno Bernardino Improved the tests and removed the hardcoded variable, according to s…
…uggestions.
efdc672
Bruno Bernardino Removing the unnecessary underscore now :) 93e4eea
Bruno Bernardino Removing unnecessary assignment cc98e99
Bruno Bernardino Updated compile beac56d
Commits on Aug 19, 2015
@jashkenas Merge pull request #4059 from BrunoBernardino/hotfix/4036-try-variabl…
…e-improvement

Closes #4036: "Try catch" optimisation
617a932
Commits on Aug 22, 2015
@lydell lydell Fix #1192: Assignment starting with object literals 2eef667
@michaelficarra michaelficarra Merge pull request #4068 from lydell/issue-1192
Fix #1192: Assignment starting with object literals
dc3e177
Commits on Aug 26, 2015
@lydell lydell Fix #4070: Improve error message for lone expansion f588ecb
Commits on Aug 27, 2015
@jashkenas Merge pull request #4071 from lydell/lone-expansion
Fix #4070: Improve error message for lone expansion
66716cd
@lydell lydell Implement ES2015-like destructuring defaults
This let's you do things like:

    fullName = ({first = 'John', last = 'Doe'}) -> "#{first} #{last}"

Note: CoffeeScrits treats `undefined` and `null` the same, and that's true in
the case of destructuring defaults as well, as opposed to ES2015 which only uses
the default value if the target is `undefined`. A similar ES2015 difference
already exists for function parameter defaults. It is important for CoffeeScript
to be consistent with itself.

    fullName2 = (first = 'John', last = 'Doe') -> "#{first} #{last}"
    assert fullName('Bob', null) is fullName2(first: 'Bob', last: null)

Fixes #1558, #3288 and #4005.
6d9553a
@jashkenas Merge pull request #4069 from lydell/destructuring-defaults
Implement ES2015-like destructuring defaults
c0c13c1
Commits on Aug 28, 2015
@lydell lydell Fix #3926: Disallow implicit objects as parameter destructuring 2c4d437
Commits on Aug 29, 2015
@lydell lydell Document destructuring defaults 10aca2a
@michaelficarra michaelficarra Merge pull request #4074 from lydell/destructuring-defaults-docs
Document destructuring defaults
ff9d511
Commits on Aug 30, 2015
@lydell lydell Improve the documentation site on smaller screens
"Smaller screens" means screens smaller than 820px wide. That's the smallest
width that the current design looks good at.

I tried to not change the current design in any way and to make as few changes
as possible.

This is what happens on smaller screens:

- The navigation bar is no longer fixed to the viewport, but always at the top
  of the page.
- The navigation bar is vertical rather than horizontal.
- CoffeeScript code is above the compiled JavaScript rather than having them
  side by side.

This allows for a larger text size, which is more compfortable to read, and no
horizontal scrolling, which many find difficult to use.
874628b
@lydell lydell Remove unnecessary blank lines at EOF in examples
On less wide screens, where the CoffeeScript is above the JavaScript, those
lines resulted in an unnecessarily high box of CoffeeScript code.
5095e02
@lydell lydell Git rid of the deprecated `<tt>` tag in the docs
Replaced with `<code>` tags.
0872c3d
Commits on Sep 01, 2015
@jashkenas Merge pull request #4075 from lydell/documentation-improvements
Documentation improvements
56d75ba
@jashkenas Merge pull request #4073 from lydell/issue-3926
Fix #3926: Disallow implicit objects as parameter destructuring
98dd1bf
Commits on Sep 03, 2015
@lydell lydell CoffeeScript 1.10.0 cea773e
@jashkenas Merge pull request #4079 from lydell/v1.10.0
CoffeeScript 1.10.0
f26d33d