5 ms·
How to Write CoffeeScript Efficiently
- VMG 15y agosadly, this could also be called "why it is difficult to write CoffeScript efficiently without some vim plugins"
- nilbus 15y agoCould someone explain how {@foo} = bar compiles into this.foo = bar.foo;?
- yesbabyyes 15y ago"@" is an alias for "this.", so "@foo" is the same as "this.foo". {foo} = bar is using destructuring assignment, it means, take property "foo" of bar and put it in variable foo, so {foo} = bar compiles to var foo = bar.foo;
- nilbus 15y agoThanks! It was the destructuring part that I wasn't understanding right away.
- yesbabyyes 15y agoNo problem! CoffeeScript's destructuring is really nice, IMO: [first, rest..., last] = someArray professions = programmer: studyTime: "5 years" salary: 10000 salesman: studyTime: "2 years" salary: 15000 {programmer: {salary}} = professions console.log "A programmer's salary is %s", salary EDIT: Fixed bug, "developer" should be "programmer".
- jrnkntl 15y ago{developer: {salary}} = professions
- skrebbel 15y agoShould have been renamed to "Some Vim tricks for CoffeeScript writing".
- s00pcan 15y agoI followed the link to the Syntastic plugin and can't get it to work. The version on github doesn't have the SyntasticEnable function for some reason, so I used the package on vim.org. I added the statusline changes and SyntaxEnable php to my vimrc, still does absolutely nothing. I'm not seeing anything different on my statusline when saving files and the :Errors function doesn't show anything either. Ideas?
- diploid 15y agoManually compiling your CoffeeScripts just seems archaic. Is there no equivalent to Sinatra AssetPack for node.js? Frankly, this is not an efficient workflow for CoffeeScript.
- Epeli 15y agoTry http://epeli.github.com/piler/ http://epeli.github.com/piler/