top | item 23184554 (no title) snek | 5 years ago As is mentioned in the article, u64 was used to future proof for wasm's upcoming memory64 type: https://github.com/WebAssembly/memory64/blob/master/proposal... discuss order hn newest Ericson2314|5 years ago Yeah, so what are they going to do when they then claim to need to to represent the length 2^64? Dylan16807|5 years ago That won't happen on a 64 bit machine. By the time we need that, the code will be so vastly different that trying to prepare for it now would be counterproductive. load replies (1) colejohnson66|5 years ago If you have 2^64 objects, you have a bigger problem. BubRoss|5 years ago If 32 bit is from your face to your hand, 64 bit is from you to the sun. You aren't going to need that on a single computer in your lifetime.
Ericson2314|5 years ago Yeah, so what are they going to do when they then claim to need to to represent the length 2^64? Dylan16807|5 years ago That won't happen on a 64 bit machine. By the time we need that, the code will be so vastly different that trying to prepare for it now would be counterproductive. load replies (1) colejohnson66|5 years ago If you have 2^64 objects, you have a bigger problem. BubRoss|5 years ago If 32 bit is from your face to your hand, 64 bit is from you to the sun. You aren't going to need that on a single computer in your lifetime.
Dylan16807|5 years ago That won't happen on a 64 bit machine. By the time we need that, the code will be so vastly different that trying to prepare for it now would be counterproductive. load replies (1)
BubRoss|5 years ago If 32 bit is from your face to your hand, 64 bit is from you to the sun. You aren't going to need that on a single computer in your lifetime.
Ericson2314|5 years ago
Dylan16807|5 years ago
colejohnson66|5 years ago
BubRoss|5 years ago