Wasmi v0.32 stable release preparations
Robbepop opened this issue · 0 comments
Robbepop commented
The following list contains the work required before we can release Wasmi v0.32:
- Write Wasmi blog post about the new features and performance improvements.
- Create benchmarking framework to compare Wasmi with other Wasm runtimes.
- Repository: https://github.com/wasmi-labs/wasmi-benchmarks
- Rename
EngineLimits
toEnforcedLimits
- These limits do not just reflect limits of the Wasmi
Engine
thus the current name is misleading. - All checks are currently not even performed in the
Engine
but rather in theModule
. This might change later. - PR: #1000
- These limits do not just reflect limits of the Wasmi
- Rename
LinkerBuilder::finish
method tocreate
.- We are not finalizing the building process since
LinkerBuilder
is supposed to create multipleLinker
instances thuscreate
is the better name. - Maybe even introduce a
LinkerBuilder::ready -> LinkerBuilderReady
method to prevent misusing theLinkerBuilder
type statically. Right nowLinkerBuilder::{func_wrap, func_new}
methods can be used after creation of aLinker
but will panic and with another type we could statically enforce correct usage. - PR: #1001
- We are not finalizing the building process since
- Properly mirror the most recent Wasmtime with
Store::{get_fuel, set_fuel}
.- PR: #1002
- Properly mirror the most recent Wasmtime
EngineWeak
API.- PR: #1003
- Verify that function compilation fuel charging is realistic.
- PR: #1005
- Improve Wasmtime API mirroring with minor renamings
- PR: #1011
- Unify Wasmi workspace crate versions.
- Makes publishing future Wasmi versions much simpler.
- PR: #1015