What was the motivation between implementing BBQVec in Rust and Go? Which is more mature? Can they share e2e test suites?
The Go is the more mature implementation; it's generally a lot easier to refactor Go as you're figuring things out and then can build the Rust version (which is a good bit faster)
Sharing e2e test suites (realistically, two different test binaries to run at CI time) is something I'm cleaning up right now.