Handle exact types on JS boundary in Unsubtyping#8451
Merged
Conversation
By considering exactness of types flowing in from JS, we can optimize more precisely because exact casts require fewer subtype relationships to be kept.
kripken
reviewed
Mar 11, 2026
| (func $test-out (result (ref null $super)) | ||
| (local $sub-out (ref null $sub-out)) | ||
| ;; This requires that $sub-out is a subtype of $super. Since $super flows | ||
| ;; out to JS, $sub-out will have to keep its descriptor. |
Member
There was a problem hiding this comment.
On line 991 it did not keep the descriptor...
Member
Author
There was a problem hiding this comment.
Aha, the optimization is smarter than I was. Comments updated.
kripken
approved these changes
Mar 11, 2026
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
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.
By considering exactness of types flowing in from JS, we can optimize
more precisely because exact casts require fewer subtype relationships
to be kept.