[red-knot] Improve tests relating to type inference for exception handlers#13643
Merged
AlexWaygood merged 1 commit intomainfrom Oct 5, 2024
Merged
[red-knot] Improve tests relating to type inference for exception handlers#13643AlexWaygood merged 1 commit intomainfrom
AlexWaygood merged 1 commit intomainfrom
Conversation
Contributor
|
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
1 participant
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.
Summary
As currently written, these tests break if you try to improve exception-handler control flow à la #13633, and they'll also break when we fix astral-sh/ty#238. This PR uses
reveal_typeto make them robust to future improvements in our understanding of exception-handler control-flow.Test Plan
cargo test -p red_knot_python_semantic --lib