fix: replace unwrap with expect with meaningful messages#80
Open
Deepak8858 wants to merge 1 commit into
Open
Conversation
Collaborator
|
Thank you for picking up the issue @Deepak8858! Would you be able to make the expect messages a bit more specific (i.e. what JS operation failed [e.g. failed to set an import entry] and what type conversion failed [e.g. failed to convert wasmtime::MemoryType to wasm_runtime_layer::MemoryType])? |
Owner
|
Would it be possible to enable the |
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
4 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.
Replaced many instances of
.unwrap()with.expect()with meaningful error messages to improve error reporting and debugging, as suggested in #78.Changes focus on the backend implementations where error context is most valuable.
Closes #78