I’ve been working through the WebAssembly spec recently and it’s pretty interesting, there are many design aspects I wouldn’t have chosen.
Was there anything about the spec that was surprising or frustrating to you?
Show HN: TinyWasm – A tiny WebAssembly Runtime written in Rust
11–15 of 15 posts
Re: Show HN: TinyWasm – A tiny WebAssembly Runtime written in Rust
#12I’ve been working through the WebAssembly spec recently and it’s pretty interesting, there are many design aspects I wouldn’t have chosen. Was there anything about the spec that was surprising or frustrating to you?
Flipping this around, could you elaborate on which specific design aspects you wouldn't have chosen?
Re: Show HN: TinyWasm – A tiny WebAssembly Runtime written in Rust
#13Thanks for sharing your project! How does performance change when the `unsafe` feature is disabled?
It looks like there is only one usage of `unsafe` outside of the no_std build: https://github.com/explodingcamera/tinywasm/blob/c50bae752f3...
Re: Show HN: TinyWasm – A tiny WebAssembly Runtime written in Rust
#14Thanks for sharing your project! How does performance change when the `unsafe` feature is disabled? It looks like there is only one usage of `unsafe` outside of the no_std build: https://github.com/explodingcamera/tinywasm/blob/c50bae752f3...
Yeah, the only unsafe code right now is using this trait to prevent some duplicate bounds checking when reading/writing to memories that wasn't being optimized by the rust compiler. Shouldn't be too much of a performance difference for code that's not too heavy on memory access, made about a 5-10% difference for the selfhosted benchmark if I remember correctly though.
Re: Show HN: TinyWasm – A tiny WebAssembly Runtime written in Rust
#15Thanks for sharing your project! How does performance change when the `unsafe` feature is disabled? It looks like there is only one usage of `unsafe` outside of the no_std build: https://github.com/explodingcamera/tinywasm/blob/c50bae752f3...
Yeah, the only unsafe code right now is using this trait to prevent some duplicate bounds checking when reading/writing to memories that wasn't being optimized by the rust compiler. Shouldn't be too much of a performance difference for code that's not too heavy on memory access, made about a 5-10% difference for the selfhosted benchmark if I remember correctly though.
[deleted]