Crypt Keeper 0561190cb9 Documents Memory.Read as a way to share memory between Go and Wasm (#527) ...

By testing the side-effects of Memory.Read, we ensure users who control
the underlying memory capacity can use the returned slice for
write-through access to Wasm addressible memory. Notably, this allows a
shared fixed length data structure to exist with a pointer on the Go
side and a memory offset on the Wasm side.

Signed-off-by: Adrian Cole <adrian@tetrate.io>
Co-authored-by: Takeshi Yoneda <takeshi@tetrate.io>

2022-05-06 09:56:40 +08:00

..

wasm_test.go

Isolates testify to one file, so that it is easier to remove (#460)

2022-04-14 10:05:38 +08:00

wasm.go

Documents Memory.Read as a way to share memory between Go and Wasm (#527)

2022-05-06 09:56:40 +08:00