mii/wasmer
1
0
Fork 0
mirror of https://github.com/mii443/wasmer.git synced 2025-12-04 11:48:38 +00:00
Code Issues Packages Projects Releases Wiki Activity

Update migration_to_1.0.0.md

Browse Source
This commit is contained in:
kwgchi
2021-01-14 21:54:16 +09:00
committed by GitHub
parent 98cf81c5fb
commit 955b1337d3
1 changed files with 3 additions and 3 deletions
Download Patch File Download Diff File Expand all files Collapse all files

6
docs/migration_to_1.0.0.md
View File

@@ -88,7 +88,7 @@ to implement custom compilers and engines respectively.
### Instantiating modules ### Instantiating modules
With Wasmer 0.x, instantiating a module was a matter of calling `wasmer::compiler::compile` and then calling With Wasmer 0.x, instantiating a module was a matter of calling `wasmer::compiler::compile` and then calling
`instanciate` on the compiled module. `instantiate` on the compiled module.
While simple, this did not give you full-control over Wasmer's configuration. For example, choosing another compiler While simple, this did not give you full-control over Wasmer's configuration. For example, choosing another compiler
was not straightforward. was not straightforward.
@@ -304,10 +304,10 @@ with this topic:
* [Handling Errors][errors] * [Handling Errors][errors]
* [Interrupting Execution][exit-early] * [Interrupting Execution][exit-early]
Note than with Wasmer 1.0.0, each function that is part of the API has its own kind of error. For example: Note that with Wasmer 1.0.0, each function that is part of the API has its own kind of error. For example:
* Instantiating a module may return `InstantiationError`s; * Instantiating a module may return `InstantiationError`s;
* Getting exports from the guest module may return `ExportError`s; * Getting exports from the guest module may return `ExportError`s;
* Calling a exported function may return `RuntimeError`s; * Calling an exported function may return `RuntimeError`s;
* ... * ...
### Caching modules ### Caching modules