How does parseInt behave with these? Does it now like underscores?
-
-
-
Sadly/luckily, `parseInt` cannot ever be updated as it would break the web (and likely introduce security issues). That is, `parseInt('123_456')` continues to produce `123`.
- 1 more reply
New conversation -
-
-
I rephrased my tweet and now it’s twice as fast.
End of conversation
New conversation -
-
-
Good job, any news for decorator?https://github.com/tc39/proposal-decorators …
-
Still at stage 2 with open questions.
@littledan is doing a great job championing the proposal, though, so stay tuned!
End of conversation
New conversation -
-
-
Will it be supported in JSON.parse() for configuration files etc? I suppose that would require a change in JSON spec?
-
No. It’s only a change to the ECMAScript syntax. JSON is set in stone.
End of conversation
New conversation -
-
-
"... per nibble" is that the official term? =D
- 1 more reply
New conversation -
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.
JavaScript, HTML, CSS, HTTP, performance, security, Bash, Unicode, i18n, macOS.
V8 v7.5 & Chrome 75 support underscores as separators in JavaScript numeric literals!