@mathias Did you expect anything else? This is how parseInt is works, and since there's no discrete ES6/5/4/3 switch, it has to stay.
-
-
-
@MartijnSaly I think it would have been nice to change `parseInt` to support them, if that were possible. - 1 more reply
New conversation -
-
-
@mathias parseInt behaviour is documented very well, Number('0b11') and others return NaN in recent WebKit. https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/parseInt … -
@pronebird Yeah, this was in response to the proposal to change `parseInt` to support the new ES6 prefixes. - 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.