Skip to content

Merge into upstream wasm-tools? #153

Open
@alexcrichton

Description

@alexcrichton

I wanted to open an issue on this to perhaps discuss this. Currently wasm-tools compose prints a warning (rightfully) to use wac and in the future the plan is to sunset wasm-tools compose and the wasm-compose crate entirely. That being said one of the key benefits of wasm-tools compose is that it's "always in sync" with the rest of wasm-tools, basically entirely because it's in the same repository. I like the idea of having the two in sync, so wanted to raise the question: would it makes sense to migrate this repository to living within wasm-tools?

The benefits of such a merge could be:

  • Integrated release cadence with wasm-tools
  • Up-to-date bindings to wasm-tools crates
  • Up-to-date on the latest component model features
  • (maybe) Better visibility for functionality

Downsides, however, are:

  • Monorepo vs multi-repo - CI is more complicated, sweeping changes to the monorepo are harder (e.g. not all contributors will be familiar with wac)
  • Less focused issue tracker (more monorepo vs multi-repo)
  • More frequent "breaking" releases for functionality that's probably not actually breaking

Would maintainers/folks here be interested in such a merge? Or best to keep things separate?

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions