Robin Freyler
Robin Freyler
As a reference point the `wasmi` PR that introduces reusable allocations provided roughly 10% performance boost: https://github.com/paritytech/wasmi/pull/411
> I think the best way to solve this would probably be some sort of opaque `struct FuncValidatorAllocations { ... }` which can be extracted and inserted into a validator....
> Sure yeah that also seems reasonable to me. Wasmtime has a perhaps different use case than what `wasmi` may be exercising which is what I'm trying to handle which...
> Wasmtime has a perhaps different use case than what wasmi may be exercising Yeah definitely, in `wasmi` we cannot really use multi-threading since `wasmi` is primarily executed as `no_std`...
I think it is not important to fix this urgently but it might be really nice to have a more user friendly API in the future and until then we...
The reason why I am not 100% sold on the `*Fallback` trait idea is that we'd still have lots of code dupe which we should at some point auto generate...
Looking at the [`for_each_operator`](https://docs.rs/wasmparser/0.90.0/wasmparser/macro.for_each_operator.html#) macro I see some potential in improving user experience further for using the `VisitOperator` API by splitting up the macro into smaller pieces. For example for...
I actually like your alternative idea more than mine since it minimizes the API surface instead of bloating it up with more macros. Would you be fine with me going...
Glad you like the idea! I think you are right that it would be pretty cool if crate features allowed to enable only parts of the entire Wasm spec. The...
While I like the proposal of going back to `no_std` this kind of conflicts with the other proposal to use `T: Read` as parser input instead of byte slices. We...