hardcoded Rust-type based errors are problematic #57
Conversation
This file contains 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
block that is more or less doing the same thing makes working with the error components error prone. Solution: Move the repetitive check into a macro.
client cannot simply parse them as PumpkinScript but has to parse them as the string representation of Rust errors. Solution: Introduce a new PumpkinScript error message.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Problem: When errors happen in PumpkinDB, the
client cannot simply parse them as PumpkinScript
but has to parse them as the string representation
of Rust errors.
Solution: Introduce a new PumpkinScript error
message.