You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
› wasmer run build/release.wasm
⠁ Compiling to WebAssembly abort: 0-0 in assembly/world.ts(107:7)
› wasmtime run build/release.wasm
abort: 0-0 in assembly/world.ts(107:7)
Error: failed to run main module `build/release.wasm`
Notice only "0-0" is getting output, which is what is passed into the throw.
The change of the message in the custom error class doesn't apply.
I suspect something like throw (new LocationOccupied(...)) would work, due to a quirk/optimization in how throw statements are compiled (most likely to avoid allocating an object just so the program can subsequently abort).
Activity
CountBleck commentedon Oct 27, 2025
I suspect something like
throw (new LocationOccupied(...))would work, due to a quirk/optimization in howthrowstatements are compiled (most likely to avoid allocating an object just so the program can subsequently abort).