[6.2.1][wasm] Fix @_expose(wasm)
serialization crash
#84433
Closed
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.
Explanation: #82616 added a new exposure kind for the
@_expose
attribute, but did not update the serialization format to account for the new kind. This caused a crash when serializing a module that used@_expose(wasm)
.Issues: #84196 #84140
Original PRs: #84215
Risk: Low, it only affects when using
@_expose(wasm)
Testing: Added a test.
Reviewers: @bnbarham, @MaxDesiatov