One thought I just had, @Yury Delendik what would you think of merging the wasmparser, wat, and wasmprinter repos? They sort of all change in lockstep anyway and it'd make it a lot easier to do sweeping changes (like implementing new proposals)
It could be a general "low level wasm tooling in that place" perhaps, not a home for something higher level like walrus
I had that thought as well. That's okay with me. What will be a repo name?
hm I hadn't thought that far, we could also do something bland like "wasm-tooling"
okay. I don't know what involved in merging two repos, but first step can be moving wasmparser into bytecodealliance/wat
there are not many issues opened with wasmparser -- I assume it is easy to move them by hand if needed
yeah these are all pretty small
@fitzgen (he/him) do you have thoughts on this perhaps?
I think this is a good idea, fwiw!
Yeah sounds good. Maybe we could call it WART: web assembly rust toolkit :joy:
Or maybe bugs, as in bugs bunny, to go along with WABT
But yeah the one thing missing is a wasm binary encoder
Which we could extract from walrus sometime
keep it wat, as in WebAssembly Toolkit ?
We are just naming the repo, right? Not renaming or merging the crates themselves, which are just moving?
If so, wat could be confusing since one of the crates has that name
Mostly I was joking with the names, and I agree a boring name like wasm-tools or something is a good fit
yeah I'm not thinking we should reorganize the crates at all, just merge repos
and update test suites so they're all referential
ok so how about bytecodealliance/wasm-tools
and a top-level crate that has src/bin/*.rs
for things like wasm2wat
and whatnot (probably with a -rs
suffix or something like that)
and crates/{wasmparser,wasmprinter,wat,wast}
?
I can prep the repo if that sounds good
@Alex Crichton sounds great!
@fitzgen (he/him) @Yury Delendik WDYT? https://github.com/bytecodealliance/wasm-tools
looks great!
wfm, what about history?
That repo is currently created by literally using git merge
between the all repos
so the history for each repo should be there
with one commit per repo to move everything to a sub-folder
okay, I see, it is just github
I tried to do my best when unifying the test suite
the tests/roundtrip.rs
script is pretty gnarly though
it's not entirely trivial to run all the wast tests
esp when we're juggling different implementation levels for various proposals across all the tools
ok I'll pull the trigger on this tomorrow unless an objection comes up?
Do we want to open issue(s) with announcement on merged repos?
What I'd imagine is similar to cranelift, which is to transfer all active issues as well as leaving a comment on open PRs
and otherwise updating the master branch to say it points elsewhere
I'd probably immediately read-only the wat/wasmprinter repos since they don't have open PRs
and we could read-only wasmparser eventually once prs have moved
er, read-only being "archive"
ok I'm pulling the trigger
@Alex Crichton will you publish new versions of wasmparser? or what is the process?
nah I think it's fine to do what you did before
basically just push a commit with a version and hit publish
although there's no need to publish the tail call stuff
I'm just trying to get wat/wasmparser on parity
and get wasmparser pass the current set of spec tests
but it triggers version change
shall we ensure version change goes into PR?
personally I take a look at the changes when publishing a version
so I leave it as-is in the repo until I publish
okay
then when publishing I reverse-engineer whether a bump should happen or not
although I wouldn't say it's a great system
Last updated: Dec 23 2024 at 13:07 UTC