[wasm-metadata] re-use metadata fields between modules and components #1943
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Currently the
Metadata
enum inwasm-metadata
has two variants:Module
andComponent
. Both inline all of their fields, with the only difference between the two being thatComponent
has an additionalchildren
field. This leads to a fair number of duplicate code paths.This PR adds a new enum
Payload
and changesMetadata
from an enum to a struct, which is shared between both variants ofPayload
. This makes it easier to work with, reason about, and add new metadata fields towasm-metadata
. Thanks!Summary