Skip to content

Commit

Permalink
Update migration_to_3.0.0.md
Browse files Browse the repository at this point in the history
  • Loading branch information
syrusakbary authored Sep 13, 2022
1 parent e6857d1 commit 3225852
Showing 1 changed file with 1 addition and 0 deletions.
1 change: 1 addition & 0 deletions docs/migration_to_3.0.0.md
Original file line number Diff line number Diff line change
Expand Up @@ -28,6 +28,7 @@ This version introduces the following changes to make the Wasmer API more ergono
The previous variants still exist in order to support the migration, but they have been deprecated.
4. `WasmerEnv` and associated traits and macro have been removed. To use a function environment, you will need to create a `FunctionEnv` object and pass it along when you construct the function. For convenience, these functions also exist in a variant without the environment for simpler use cases that don't need it. For the variants with the environment, it can be retrieved from the first argument of the function. Because the `WasmerEnv` and all helpers don't exists anymore, you have to import memory yourself, there isn't any per instance initialisation automatically done anymore. It's especially important in wasi use with `WasiEnv`. `Env` can be accessed from a `FunctionEnvMut<'_, WasiEnv>` using `FunctionEnvMut::data()` or `FunctionEnvMut::data_mut()`.
5. The `Engine`s API has been simplified, Instead of the user choosing and setting up an engine explicitly, everything now uses a single engine. All functionalities of the `universal`, `staticlib` and `dylib` engines should be available in this new engine unless explicitly stated as unsupported.
6. Loupe has been removed. Memory inspection should be done manually

## How to use Wasmer 3.0.0

Expand Down

0 comments on commit 3225852

Please sign in to comment.