@Dan Gohman @Alex Crichton @Jakub Konka how do y'all feel about a PR that lands wiggle (and its subcrates) into the wasmtime repository, so we can publish a crates.io release as part of an ordinary wasmtime release?
i know the PR to use wiggle in wasi-common is still not quite done, and im keen to pitch in on that, but in the meantime it would be useful to me to have a crates.io release to point my lucet integration at. (presently just using a git dependency)
Makes sense to me! Lemme quickly come up with such a PR! Oh, like with migrating wasi-common and cranelift, I’ll preserve the git history for posterity if for nothing else.
Waiting for your review guys: https://github.com/bytecodealliance/wasmtime/pull/1278
Sounds reasonable to me!
In preparation for landing #1278, I've now made wiggle
repo read-only
My one bit of feedback is we should put it at crates/wiggle. I think (hope?) we get lots of use outside of wasi-common :)
SGTM! Should be pretty easy to fix in the PR!
On a similar note, I expect we'll eventually want to move yanix/winx out to crates/ at some point too.
Yep, figured as much ;-)
Pat Hickey said:
My one bit of feedback is we should put it at crates/wiggle. I think (hope?) we get lots of use outside of wasi-common :)
And done :-)
While we're here, do you think we should split tests in the CI into something that's more context oriented? Separately running tests for WASI and related, wiggle, etc? I feel currently it's quite difficulty to work out what is going on in the CI
Exciting times ahead, wiggle
just landed ;-)
:wavy_dash:️It's Wiggle Time:wavy_dash:️
This will never get old :D
Last updated: Nov 22 2024 at 16:03 UTC