3 ms·
Let's get actual integers into JS! c'mon, I can't actually represent 64 bit IDs properly! This affects a big analytics product you have probably used!
by nimish 8y ago
Let's get actual integers into JS! c'mon, I can't actually represent 64 bit IDs properly! This affects a big analytics product you have probably used!
- Waterluvian 8y agoAs this isn't my realm of expertise, I'm curious to understand how bigint would fail to meet your needs.
- nimish 8y agoThere's no guarantee that it will specialize down to machine integers. I don't need arbitrary precision; I need fast, fixed precision. If the proposals guaranteed specialization I'd be much happier but I don't think they do. But it's way better than the status quo.
- millstone 8y agoAre you performing arithmetic on 64 bit "IDs?" That seems unlikely, so where would any savings come from?
- andreareina 8y agoComparison (as when doing e.g. an index scan) would still be affected, no?
- nimish 8y agoComparisons and constructing indexes, and hashing. All need the ALU. And of course we use them for bitmaps.
- zzo38computer 8y agoI think no such guarantee is needed as that is beyond the scope of the specification, I think. If you do need that you can use C or WebAssembly (or you can specifically use an implementation which guarantees it).