Files
wasmtime/crates/runtime
Alex Crichton d8d4bf81b2 Reimplement how instance exports are stored/loaded (#2984)
* Reimplement how instance exports are stored/loaded

This commit internally refactors how instance exports are handled and
fixes two issues. One issue is that when we instantiate an instance we
no longer forcibly load all items from the instance immediately,
deferring insertion of each item into the store data tables to happen
later as necessary. The next issue is that repeated calls to
`Caller::get_export` would continuously insert items into the store data
tables. While working as intended this was undesirable because it would
continuously push onto a vector that only got deallocated once the
entire store was deallocate. Now it's routed to `Instance::get_export`
which doesn't have this behavior.

Closes #2916
Closes #2983

* Just define our own `Either`
2021-06-17 14:27:48 -05:00
..
2021-06-09 14:00:13 -05:00
2019-11-08 06:35:40 -08:00
2020-03-23 09:58:08 -07:00

This is the wasmtime-runtime crate, which contains wasm runtime library support, supporting the wasm ABI used by wasmtime-environ, wasmtime-jit, and wasmtime-obj.

This crate does not make a host vs. target distinction; it is meant to be compiled for the target.

Most users will want to use the main wasmtime crate instead of using this crate directly.