4 ms·
A bit of that is in this release as well, thanks to Jason Walton. https://github.com/jashkenas/coffee-script/blob/master/src/grammar.coffee#L43-L56 https://gith
by jashkenas 14y ago
A bit of that is in this release as well, thanks to Jason Walton. https://github.com/jashkenas/coffee-script/blob/master/src/grammar.coffee#L43-L56 https://github.com/jashkenas/coffee-script/blob/master/src/g...
Source location information is now preserved through the parse, although it's not yet being emitted as a source map just yet. If you want to use CoffeeScript source maps today, feel free to use the Redux compiler, which does them just fine. Michael also has some other tools to make source maps even more convenient: https://github.com/michaelficarra/commonjs-everywhere https://github.com/michaelficarra/commonjs-everywhere
That said, I don't personally care for source maps all that much, placing a higher priority on generating readable and straightforward JavaScript output. Things like Literate CoffeeScript rank higher on the priority list.
- coldtea 14y agoThanks for the response (well, given my tone). But I think this literate thing never caught on for a reason. And I'd say the reason is marginal returns (over comments and clean code) and too much fuss. As for the "entitlement", it's because people have been saying source maps would came to CS for 2 years now, and I've seen nothing related yet (even the crowd-funded project is not there).