Enable semver-compatible matching of import/export lookups in targets #168
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.
Previously in targets validation the lookup of imports/exports required an exact match. This PR switches to using a NameMap that enables semver-compatible matching lookups.
NOTE: This PR borrows the implementation of NameMap from wasmtime.
As a follow up i'd like to re-use this NameMap to consolidate semver-compatible imports/exports during encoding so that only the maximal semver-compatible range is used.