Hacker News new | past | comments | ask | show | jobs | submit login

Yeah, mythz (not you, I trust) used the same dismissive approach here:

https://news.ycombinator.com/item?id=8308578

after first asking someone to cite such a problem.

AFAICT the "isn't a problem in practice" happy-talk is all coming from Dart insiders. Does this shoe fit?

Anyway, it's a real Dart bug that drives potential users away. And why is JS bignum support -- which Google for-sure could have championed in Ecma TC39 and prototype-implemented in V8 -- just an "It would be nice" thing?

(It is not difficult to support suffixes for new value types, e.g. 0m for decimal and 0n or better for bignum. This is on the ES7 agenda. For more on range analysis and other/better optimization options, see https://news.ycombinator.com/item?id=6950475.)

Trusting checked-mode test coverage is bold in light of this bug, where bold might be "stupid" or "you're fired". As I wrote once in this thread already, Murphy was an optimist.




I agree this needs to be fixed in JS. And I have been following the ES strawmen/proposals. Not sure if I like suffixes. The approach in Dart seems to work well too.

In JS the overflow is often silent and is easy to miss. Since the DartVM can throw an exception on overflow this makes it easier to catch. So the Dart toolchain is an improvement, but also not ideal.

Where correctness is important there are also 32/64bit and bignum libraries which can be compiled to js but are slow.

Edit: Mythz used exactly the same phrase. Jinx.




Consider applying for YC's Spring batch! Applications are open till Feb 11.

Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: