Hacker News
new
|
past
|
comments
|
ask
|
show
|
jobs
|
submit
login
arve0
on June 27, 2017
|
parent
|
context
|
favorite
| on:
TC39, ECMAScript, and the Future of JavaScript
Which wtfs bite you the most?
I can't remember being bitten lately, maybe I have a blind spot.
true_religion
on June 27, 2017
|
next
[–]
In a lot of the places where NaN is generated, I would prefer it if an error was thrown.
bryanrasmussen
on June 27, 2017
|
parent
|
next
[–]
I think all JS NaNs are quiet NaNs when sometimes signaling NaNs should be supported/be preferable
https://en.wikipedia.org/wiki/NaN#Signaling_NaN
gear54rus
on June 27, 2017
|
prev
[–]
forEach returns undefined. Why would you not just return the same array for easy chaining?
brad0
on June 27, 2017
|
parent
[–]
Probably to make a distinction between map() which returns a new array. If forEach returned the same array I believe you'd would see a lot more bugs.
Guidelines
|
FAQ
|
Lists
|
API
|
Security
|
Legal
|
Apply to YC
|
Contact
Search:
I can't remember being bitten lately, maybe I have a blind spot.