Add support for ref.null constant in WAST expectations#8076
Merged
Conversation
tlively
approved these changes
Dec 1, 2025
Member
tlively
left a comment
tlively
left a comment
There was a problem hiding this comment.
LGTM with updated failure reason.
stevenfontanella
changed the base branch from
module-definition-and-instance-cp
to
main
stevenfontanella
force-pushed
the
refnull
branch
from
92115c8 to
96e87ee
Compare
91 tasks
91 tasks
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
Fixes
ref_null.wastspec test and partially fixesref_is_null.wastandselect.wast.