Now that we are aware, we'll discuss the topic (incl. considering Node.js concerns/requests) for next @TC39. 4/4
-
-
just agreed: try BigInt (name & suffix TBD, but L suffix is out) as alternative to Int64,
@littledan among champions.2 replies 3 retweets 6 likes -
-
Yes, idea is engines optimize to int64 on CPUs where it wins & type inference blesses; no "do both" (yet).
1 reply 0 retweets 0 likes -
-
BigInt based on same value types future-proofing for operators/literals; can't do both; progress required.
1 reply 0 retweets 0 likes -
Replying to @BrendanEich @wycats and
Let's see what
@littledan & co-champion, who may be@jfbastien - "vice" champion haha - can do. I'm game & I'll help.1 reply 2 retweets 2 likes -
Replying to @BrendanEich @wycats and
"vice" sounds about right for "always bet on JavaScript 🂡". I'll drink to that
!
1 reply 0 retweets 2 likes -
-
Replying to @BrendanEich @wycats and
I unfortunately won't be at tonight's festivities. Child-feeding class is my kinda fun now.
2 replies 0 retweets 2 likes
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.
