T0b1/wasmtime
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

Adjust release notes for Caller type (#1393)

Browse Source 
Take into account comments on #1392
This commit is contained in:
Alex Crichton
2020-03-24 15:17:14 -05:00
committed by GitHub
parent addb31a266
commit 358f957a49
1 changed files with 4 additions and 1 deletions
Download Patch File Download Diff File Expand all files Collapse all files

5
RELEASES.md
View File

@@ -27,7 +27,10 @@ Unreleased
* The `wasmtime::Caller` type now exists as a first-class way to access the * The `wasmtime::Caller` type now exists as a first-class way to access the
caller's exports, namely memory, when implementing host APIs. This can be the caller's exports, namely memory, when implementing host APIs. This can be the
first argument of functions defined with `Func::new` or `Func::wrap` which first argument of functions defined with `Func::new` or `Func::wrap` which
allows easily implementing methods which take a pointer into wasm memory. allows easily implementing methods which take a pointer into wasm memory. Note
that this only works for accessing the caller's `Memory` for now and it must
be exported. This will eventually be replaced with a more general-purpose
mechanism like interface types.
[#1290](https://github.com/bytecodealliance/wasmtime/pull/1290) [#1290](https://github.com/bytecodealliance/wasmtime/pull/1290)
* The bulk memory proposal has been fully implemented. * The bulk memory proposal has been fully implemented.