Andrew Brown
Andrew Brown
Yeah, exactly. And maybe setting some environment variables. Possibly: ``` FROM ubuntu:18.04 WORKDIR / RUN apt update && apt install -y wget RUN wget https://github.com/WebAssembly/wasi-sdk/releases/download/wasi-sdk-12/wasi-sdk-12.0-linux.tar.gz RUN tar xvf wasi-sdk-12.0-linux.tar.gz ENV...
I think we would want to wire it up with the CI somehow so that, upon release, some `docker push ...` command is run.
Ok, I think I understand [from the docs](https://docs.github.com/en/actions/guides/publishing-docker-images) how to do this and am trying to figure out if the owner of [the webassembly name on DockerHub](https://hub.docker.com/u/webassembly) will share it...
The way I am thinking about this right now: what if we added `Config::orphaned_stack_values()` and allowed it to be configured with, ```rust /// What to do with values left on...
I think it's deprecated? I don't see it in the WAT specification for [control instructions](https://webassembly.github.io/spec/core/text/instructions.html#control-instructions).
cc: @alexcrichton, guess that crash we saw wasn't the `spec` interpreter after all.
I would prefer fewer `raw_bitcasts` if at all possible? I'm not very fond of it...
SIMD support added by @conrad-watt in #3843.
Is this because those types are not used by the WebAssembly SIMD instructions for narrowing?
Does `publish.rs` need to change?