Source maps

[boris-petrov]

CoffeeScript now supports source maps and using this we can use it in node.js. Any plans to support that in Iced too?

[maxtaco]

Hi Boris, Yeah, of course, I just need to get a few hours. I have a feeling it's going to be a big merge.

Here's a question for you. Do you use awaited statements as expressions, with something like:

x = (await foo defer _) + (await bar defer _)

I was planning on getting rid of this feature to keep ICS closer to CS. It's this feature the accounts for 50% or so of the patch.

[boris-petrov]

Hey,

Yep, I'm pretty sure it's going to be one hell of a merge. :)

About the awaited statement as an expression - no, I do not use that. I haven't found it useful. Same goes for autocb actually. I was using it in the beginning but after a while I decided that it's not obvious when I use return statements whether that's calling a callback or not (as I have to see the name of the argument) and that was the end of it. :)

If it were up to me, I would drop that feature if it is really 50% of the code to be merged.

Thanks!

[mkadan]

Hi maxtaco!

Any progress on introducing source maps? This will be a really nice feature, as WebStorm 6 supports them for debugging now.

[maxtaco]

HI guys, thanks so much for all of your enthusiasm. I spent a few hours on it this weekend, but nothing solid yet. I promise I haven't dropped the ball and still hope to get to it soon.

[maxtaco]

Good news folks! I'm closing on a release here. As part of this release, I'm going to do a few major things:

• Move development to a new repository: https://github.com/iced-coffee-script/iced-coffee-script. This is for Google-ability (as per an earlier issue) and also it will be an organization, not my personal project. Eventually you can all help me!
• I think at this point it makes sense to move from a rebase to a merge strategy for keeping current with changes in the upstream jashkenas repository.
• Removing use of awaited statements as expressions that can be assigned to, etc. Eventually, I want to pepper nodes.iced with code to throw a syntax error if this new requirement is violated directly or recursively. Still working on that.
• A fresh merge, cleaning up the patch, and condensing the commits to a small handfull.
• And of course, 1.6.2 support, with source-maps

The downside to all of this is that we'll lose the Issue tracker from the old repository. But I think overall it's worth it.

[mkadan]

Hi Maxwell.

Very good news indeed! Looking forward to all these changes coming live.

2013/4/23 Maxwell Krohn notifications@github.com

Good news folks! I'm closing on a release here. As part of this release, I'm going to do a few major things:

• Move development to a new repository: https://github.com/iced-coffee-script/iced-coffee-script. This is for Google-ability (as per an earlier issue) and also it will be an organization, not my personal project. Eventually you can all help me!
• I think at this point it makes sense to move from a rebase to a merge strategy for keeping current with changes in the upstream jashkenas repository.
• Removing use of awaited statements as expressions that can be assigned to, etc. Eventually, I want to pepper nodes.iced with code to throw a syntax error if this new requirement is violated directly or recursively. Still working on that.
• A fresh merge, cleaning up the patch, and condensing the commits to a small handfull.
• And of course, 1.6.2 support, with source-maps

The downside to all of this is that we'll lose the Issue tracker from the old repository. But I think overall it's worth it.

— Reply to this email directly or view it on GitHubhttps://github.com/maxtaco/coffee-script/issues/63#issuecomment-16827214 .

[maxtaco]

Change of plans, I'm going to stay in this repository, but on the iced2 branch. There are some remaining issues to work out, but keeping it here will keep the stars and the issues in place.

[maxtaco]

Merged in 1.6.2a. Let me know if you see any issues. Thanks everyone for your patience.