brain0

Thanks for your response. I may reply in more detail later, these are just some additional thoughts after finally understanding how the pre-opened directories work. > WASI doesn't provide APIs...

I've been looking into this by starting to prototype a bit. I first created a proc macro that parses the witx and creates "native" representations of the WASI types. It...

> That sounds great! The one issue with this is that we need types that are always valid when they come from Wasm. So all enums coming from the Wasm...

Okay, here it goes. Source: https://github.com/brain0/wasmer-wasi-alternative-prototype Docs: https://wasi.bchlr.de/wasmer_wasi_alternative_prototype/

> Hmm, I'm not sure, I learned in a discussion in #1249 that MIRI at least does not complain about mutable aliasing when dealing with pointers. See https://play.rust-lang.org/?version=stable&mode=debug&edition=2018&gist=bdd96fbd2d4b21e9312cd1d4b62317a9 for example...

As you can see above, I prototyped a different approach for WASI last year. It included (incomplete) code generation from the witx file and a different approach to file system...