Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Parser] Fix error message on required reftype #6666

Merged
merged 2 commits into from
Jun 14, 2024
Merged

Conversation

tlively
Copy link
Member

@tlively tlively commented Jun 14, 2024

Not all uses of the reftype parser handled the fact that it returned a
MaybeResult. Change its name to maybeReftype, add a new reftype parser
that returns an error if there is no reftype, and update all the use sites.

Fixes #6655.

@tlively tlively requested a review from kripken June 14, 2024 20:52
As an abbreviation, a `typeuse` can be given as just a list of parameters and
results, in which case it corresponds to the index of the first function type
with the same parameters and results. That function type must also be an MVP
function type, i.e. it cannot have a nontrivial rec group, be non-final, or have
a declared supertype. The parser did not previously implement all of these rules.
Not all uses of the `reftype` parser handled the fact that it returned a
`MaybeResult`. Change its name to `maybeReftype`, add a new `reftype` parser
that returns an error if there is no reftype, and update all the use sites.

Fixes #6655.
Base automatically changed from parser-typeuse-reqs to main June 14, 2024 23:00
@tlively tlively merged commit cf2725b into main Jun 14, 2024
13 checks passed
@tlively tlively deleted the parser-maybe-reftype branch June 14, 2024 23:28
@gkdn gkdn mentioned this pull request Aug 31, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Assertion when assembling ref.cast with a no ref type
2 participants