-
Notifications
You must be signed in to change notification settings - Fork 1.8k
[ty] Only normalize constraint bounds for display #21516
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Merged
Merged
Changes from all commits
Commits
Show all changes
7 commits
Select commit
Hold shift + click to select a range
502ca94
only normalize on display
dcreager 4d1026d
dedup consequents
dcreager ed9cab8
add derived constraints too
dcreager faa6db8
add implications
dcreager dfa73a9
Update crates/ty_python_semantic/src/types/constraints.rs
dcreager fb2c502
reword comment
dcreager 7168ee8
Merge remote-tracking branch 'origin/main' into dcreager/abnormal
dcreager File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
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
Oops, something went wrong.
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The explanation above seems to imply that we could (should?) return early here? Because if
a → balways impliesa ∧ b = a, then the code below would otherwise add two additionala → bimplications and onea → aimplication, both of which seem unnecessary?There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
There are other protections in place against both of those: The
single_implicationsandpair_implicationsmaps now have sets to store all of the consequents, so two copies ofa → bwill automatically get de-duped, no matter how they're created. And similarly,add_single_implicationandadd_pair_implicationwill skip any sequent of the forma → a,a ∧ b → a, ora ∧ b → b, since they are not useful.