Francesco Zardi

Reading the comments to a relevant issue in the miri repo (rust-lang/miri#1916), it seems like miri does not support `wasm32-unknown-unknown`. Maybe I misuderstood something?

Sure thing! I'll be working towards closing this issue

Sure!

To test how this works when a clippy lint is triggered, I tried creating a dummy PR [here](https://github.com/frazar/zerocopy/pull/4) that should trigger a clippy warning.

Sure! I didn't realize that clippy warning could differ based on toolchain/target.

Unfortunately, I didn't have much time to experiment with this. Surely your solution would be easier. I thought the GitHub Action could be more convenient since it can also show...

Oh, I see! I didn't understand this limitation existed.. Trying now the changes you suggested.

So, it seems like some clippy errors are triggered when the "alloc" features is enabled! Can reproduce locally with: ``` $ cargo clippy --features "alloc" ```

Rebased and pushed. Looks good now!

Through the powers of web.archive.org, I think I have found a copy of the original pictures.