aboutsummaryrefslogtreecommitdiffhomepage
path: root/builder/sizes_test.go
diff options
context:
space:
mode:
authorAyke van Laethem <[email protected]>2023-04-30 17:54:03 +0200
committerRon Evans <[email protected]>2023-06-17 18:08:09 +0200
commit4d2a6d2bbeef8db2a2e9714f3d91372f89bc9b80 (patch)
tree1ed8cd1b81439b41d91fadd3df66ad5a8f8aaba2 /builder/sizes_test.go
parent6d5f4c4be2096b0d84dffbd7a0960fd6249c4b6b (diff)
downloadtinygo-4d2a6d2bbeef8db2a2e9714f3d91372f89bc9b80.tar.gz
tinygo-4d2a6d2bbeef8db2a2e9714f3d91372f89bc9b80.zip
wasm: remove i64 workaround, use BigInt instead
Browsers previously didn't support the WebAssembly i64 type, so we had to work around that limitation by converting the LLVM i64 type to something else. Some people used a pair of i32 values, but we used a pointer to a stack allocated i64. Now however, all major browsers and Node.js do support WebAssembly BigInt integration so that i64 values can be passed back and forth between WebAssembly and JavaScript easily. Therefore, I think the time has come to drop support for this workaround. For more information: https://v8.dev/features/wasm-bigint (note that TinyGo has used a slightly different way of passing i64 values between JS and Wasm). For information on browser support: https://webassembly.org/roadmap/
Diffstat (limited to 'builder/sizes_test.go')
0 files changed, 0 insertions, 0 deletions