Skip to content

Conversation

@dicej
Copy link
Collaborator

@dicej dicej commented Jul 31, 2025

If the module exports a function with the [async-lift] prefix (rather than the [async-lift-stackful] one), then we must be able to match that up with a corresponding callback function; otherwise, we fail validation.

Prior to this fix, we'd silently generate an invalid component and leave it to wasmparser to notice, which is bad form, plus the diagnostic message wasn't very helpful.

If the module exports a function with the `[async-lift]` prefix (rather than the
`[async-lift-stackful]` one), then we must be able to match that up with a
corresponding callback function; otherwise, we fail validation.

Prior to this fix, we'd silently generate an invalid component and leave it to
`wasmparser` to notice, which is bad form, plus the diagnostic message wasn't
very helpful.

Signed-off-by: Joel Dice <joel.dice@fermyon.com>
@dicej dicej requested a review from a team as a code owner July 31, 2025 20:42
@dicej dicej requested review from fitzgen and removed request for a team July 31, 2025 20:42
@alexcrichton alexcrichton added this pull request to the merge queue Jul 31, 2025
Merged via the queue into bytecodealliance:main with commit c2fc211 Jul 31, 2025
34 checks passed
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.

2 participants