Julien Cretin

The [multi-memory](https://github.com/WebAssembly/multi-memory) WebAssembly proposal might help avoiding copies for shared buffers.

A guideline could be: - An applet is a WebAssembly store. This is at least useful for security to prevent state being accidentally shared between applets. But this is probably...

EDIT: Made obsolete by #102 and following PRs. Possible solution for `cargo install`: - Use `--root=_/root` to install locally. It might be a good idea to put all generated and...

Actually, I think I have a concrete example where it is beneficial (and not just more expressive) to be able to choose the `Deserialize` lifetime parameter from the `impl` parameters....

Here's a concrete example: https://github.com/ia0/wasefire/blob/96c8e4e29d554346b71b297668b2b7337dbf3455/crates/protocol/src/lib.rs#L64 That said, I'm not convinced it's something I like. Ideally I want to use `for Deserialize

I'm implementing an RPC protocol from a host to a device using an top-level enum whose discriminant indicates the RPC function: ```rust enum Api), PlatformVersion(T::Type), UpdatePlatform), // etc... but always...

> Have you considered [bincode](https://github.com/bincode-org/bincode)? No I did not. Thanks for the link! From what I can see it has the same issues as serde: - You can't choose the...

> note that on windows machines the symlink stuff does not work well Indeed, we don't support development on Windows, only the published library and binary are cross-platform. However, this...

> Gate the different models behind a crate feature Yes, that's one option, but we want to possibly go further (depending on user need). The current design I have in...

> docs.rs already hides features with a `__` prefix, and this is a de-facto standard it in the ecosystem. I think this could simply be documented as the official way...