Arrow functions are one of the improvements from JS Harmony (which was ratified last night).
This commit moves them from "behind the experimental flag" to "shipping by default" in Chromium. It's a pretty big deal to people who write JS for a living.
I'm glad it's finally arriving, it been working in Firefox for quite a long time and I'm happy to see v8 implementing this ! Arrow functions are so much nicer to read and use.
Can you not see the typos possible with this? The less characters you use for something, the more error prone. There's a reason we don't write in regular expression syntax.
Do the stack traces for native arrow functions show up in the stack trace as anonymous functions or is only the parent function registered in the stack trace.
Anyone have any idea when destructuring assignment is going to make it into v8?
That is one of the features my colleagues most cite as justification for using babel.js (I wouldn't mind destructuring assigment either). I would love to be able to avoid transpilation since it adds overhead from making out our toolchain more complex and makes debugging more difficult because stack traces and line numbers don't necessarily match up.
You can tell by the number of CLs that a lot of work has been done already but there are a few more still in progress. It's probably still a few weeks out.
Disclaimer: I don't speak for the V8 team, I'm just an interested onlooker.
[+] [-] feld|10 years ago|reply
edit: after following 4 links I finally found the bug report about it
https://code.google.com/p/v8/issues/detail?id=2700
[+] [-] bsimpson|10 years ago|reply
This commit moves them from "behind the experimental flag" to "shipping by default" in Chromium. It's a pretty big deal to people who write JS for a living.
[+] [-] towelguy|10 years ago|reply
[+] [-] JeremyBanks|10 years ago|reply
[+] [-] teraflop|10 years ago|reply
[+] [-] rubiquity|10 years ago|reply
[+] [-] realusername|10 years ago|reply
[+] [-] eueueu|10 years ago|reply
Maybe I'm just getting old!
[+] [-] malandrew|10 years ago|reply
[+] [-] davexunit|10 years ago|reply
[+] [-] malandrew|10 years ago|reply
[+] [-] nawitus|10 years ago|reply
[+] [-] malandrew|10 years ago|reply
That is one of the features my colleagues most cite as justification for using babel.js (I wouldn't mind destructuring assigment either). I would love to be able to avoid transpilation since it adds overhead from making out our toolchain more complex and makes debugging more difficult because stack traces and line numbers don't necessarily match up.
[+] [-] bnoordhuis|10 years ago|reply
You can tell by the number of CLs that a lot of work has been done already but there are a few more still in progress. It's probably still a few weeks out.
Disclaimer: I don't speak for the V8 team, I'm just an interested onlooker.
[+] [-] cozuya|10 years ago|reply
[+] [-] awalGarg|10 years ago|reply
[1] - https://code.google.com/p/v8/issues/detail?id=2700#c47
[+] [-] z3t4|10 years ago|reply
Sometimes the code explains itself though!?