4/ protobufs & similar, not crypto or num/fin/sci, just machine ints.
-
-
Replying to @BrendanEich @rmhrisk and
In mtg ppl said "just use BigInt" but it brings new perf cliff risk.+
1 reply 0 retweets 0 likes -
Replying to @BrendanEich @rmhrisk and
Either Int64 or BigInt could fall off boxed heap-alloc cliff, true. +
1 reply 0 retweets 0 likes -
Replying to @BrendanEich @rmhrisk and
But w/ Int64 you can avoid falling off overflow int64 (note lower i)+
1 reply 0 retweets 0 likes -
Replying to @BrendanEich @rmhrisk and
internal optimized to 64-bit fast path due to overflow; BigInt can't.
1 reply 0 retweets 1 like -
-
Replying to @jfbastien @BrendanEich and
for whatever clamp-to-i64 equivalent we come up with.
1 reply 0 retweets 0 likes -
Replying to @jfbastien @rmhrisk and
It would be ugly & verbose w/o Int64: bn & 0xFFFFFFFFFFFFFFFFn.
3 replies 0 retweets 0 likes -
-
Replying to @jfbastien @BrendanEich and
how many times this will have to be done throughout the code? ;)
2 replies 0 retweets 0 likes
Replying to @indutny @jfbastien and
The TypeScript transpiler will handle this transparently for you.
11:21 AM - 26 Jan 2017
0 replies
0 retweets
1 like
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.