refactor: clarify error msg. for de-allocated ResourceAny#12751
Merged
alexcrichton merged 2 commits intobytecodealliance:mainfrom Mar 10, 2026
Merged
refactor: clarify error msg. for de-allocated ResourceAny#12751alexcrichton merged 2 commits intobytecodealliance:mainfrom
ResourceAny#12751alexcrichton merged 2 commits intobytecodealliance:mainfrom
Conversation
The error message used to state that this happens because the type of the resource changed, but actually this can also happen with the very same type if the resource was already de-allocated. Clarifying the error message might safe some `wasmtime` users some long debugging sessions. See bytecodealliance#12465.
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.
The error message used to state that this happens because the type of the resource changed, but actually this can also happen with the very same type if the resource was already de-allocated. Clarifying the error message might safe some
wasmtimeusers some long debugging sessions.See #12465.