You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
While I've browsed your discussions a bit, I can't say that I've read everything so apologies if this has been brought up before.
Did you consider a 1to2 code conversion tool, a-la python's 2to3? Having one would allow more aggressive changes in scoping and for statements and maybe other places where backwards compat is inconvenient. ES2015 is sometimes awkward because it didn't drop compatibility and I would hate to see the same thing happen to coffeescript.
I might be able to invest some time in this if need be.
The text was updated successfully, but these errors were encountered:
At the moment there aren’t any syntax changes planned. Classes will be the biggest change, but the change is only what current CoffeeScript compiles to. There might be things that become disallowed, like class properties, but if that’s the case then those properties will throw compilation errors. You can see #4311 with regard to arrow functions and rest parameter syntax; basically we’re going to great lengths to preserve the current syntax.
As we’re nearing the release of 2.0.0, it looks like there are no significant syntax changes. The most common one is needing to convert super to super().
From @za-creature on 2016-10-13 17:37
Hi guys,
While I've browsed your discussions a bit, I can't say that I've read everything so apologies if this has been brought up before.
Did you consider a 1to2 code conversion tool, a-la python's 2to3? Having one would allow more aggressive changes in scoping and for statements and maybe other places where backwards compat is inconvenient. ES2015 is sometimes awkward because it didn't drop compatibility and I would hate to see the same thing happen to coffeescript.
I might be able to invest some time in this if need be.
The text was updated successfully, but these errors were encountered: