Skip to content

Adjust rules for canonical interface names - #711

Open
alexcrichton wants to merge 1 commit into
WebAssembly:mainfrom
alexcrichton:adjust-canon-versions
Open

Adjust rules for canonical interface names#711
alexcrichton wants to merge 1 commit into
WebAssembly:mainfrom
alexcrichton:adjust-canon-versions

Conversation

@alexcrichton

Copy link
Copy Markdown
Collaborator

Tweak the string-splitting to more closely match the intent of versions found in tooling, specifically:

  • Document that build metadata (+foo in 0.0.1+foo) is always split out and not part of the canonical name.
  • Don't split out pre-release information since pre-release versions are incompatible with all other versions.

This additionally matches preexisting merging behavior in wit-component as discovered in bytecodealliance/wasm-tools#2622

Tweak the string-splitting to more closely match the intent of versions
found in tooling, specifically:

* Document that build metadata (`+foo` in `0.0.1+foo`) is always split
  out and not part of the canonical name.
* Don't split out pre-release information since pre-release versions are
  incompatible with all other versions.

This additionally matches preexisting merging behavior in
`wit-component` as discovered in bytecodealliance/wasm-tools#2622
@alexcrichton

Copy link
Copy Markdown
Collaborator Author

cc @chenyan2002 this is in response to this comment thread where I believe the intention is that the preexisting split point used in wit-component should be the same as the one for canonical names.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants