wasm-bindgen/crates/backend
Alex Crichton 6796bc6895 Communicate exceptions through global memory
Instead of allocating space on the stack and returning a pointer we
should be able to use a single global memory location to communicate
this error payload information. This shouldn't run into any reentrancy
issues since it's only stored just before returning to wasm and it's
always read just after returning from wasm.
2019-06-11 11:41:05 -07:00
..
src Communicate exceptions through global memory 2019-06-11 11:41:05 -07:00
Cargo.toml Bump to 0.2.45 2019-05-20 09:44:03 -07:00