Andrew Brown

> To be clear, would I want to include or would it be located elsewhere? @grynspan, I think it would be ``?

If we did this exclusively in wasi-libc it could look like: https://github.com/WebAssembly/wasi-libc/pull/534.

I'm not really working on this any more.

This seems like the kind of thing @sbc100 has been for: it would certainly make it easier to compile more things. I'm pretty neutral and your "extra macro to just...

cc: @shschaefer, @radu-matei, @geekbeast

I brought this up a while ago here: https://github.com/bytecodealliance/actions/issues/12. I agree we need this! @konsumer, are you willing to upstream your action to the https://github.com/bytecodealliance/actions repository? That would be a...

I got nerd-sniped a bit and, after some clicking around, I am leaning toward placing any downloaded artifacts into `$RUNNER_TOOL_CACHE`. It's one of the [default environment variables](https://docs.github.com/en/actions/how-tos/writing-workflows/choosing-what-your-workflow-does/store-information-in-variables#default-environment-variables) in a runner...

Sure, I'll comment on a few of the issues in your repository. Re: "where to put this," I just spent some time discussing this with other maintainers; here are some...

@lum1n0us, what is going on here is that OpenVINO has switched to a new API and the Rust bindings that Wasmtime uses need to be updated to the newly-released v0.7.1...

This code scan is configured to run on every PR _and_ on Tuesdays. The results of code scans during a PR should be available in the PR itself ([docs](https://docs.github.com/en/code-security/code-scanning/managing-code-scanning-alerts/triaging-code-scanning-alerts-in-pull-requests#viewing-an-alert-on-your-pull-request)... IIUC)....