Skip to content

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
tlively added 2 commits June 14, 2024 14:56
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.
@tlively tlively force-pushed the parser-typeuse-reqs branch from 807c941 to 427de00 Compare June 14, 2024 21:59
@tlively tlively force-pushed the parser-maybe-reftype branch from fb01220 to a15ab53 Compare June 14, 2024 21:59
Base automatically changed from parser-typeuse-reqs to main June 14, 2024 23:00
@tlively tlively merged commit cf2725b into main Jun 14, 2024
@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

3 participants