Runtime jet type check#361
Merged
apoelstra merged 1 commit intoBlockstreamResearch:masterfrom May 5, 2026
Merged
Conversation
Contributor
Author
|
@apoelstra At first I thought about returning a concrete error type, but the The current approach is still better than what we had before, we catch type mismatches at construction time instead of during execution. |
Collaborator
|
Yeah, I think panicking is fine. It's definitely a programming error if jets wind up getting mixed. We'll likely need some experience with the API to figure out what tools we need to provide to minimize chances of this error. |
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.
This PR introduces a runtime jet type check in the Context to prevent unintended behavior.