Skip to content

Comments

[ty] Ensure that bool | AlwaysFalsy is considered equivalent to Literal[True] | AlwaysFalsy#15784

Closed
AlexWaygood wants to merge 5 commits intomainfrom
alex/truthy-unions-7
Closed

[ty] Ensure that bool | AlwaysFalsy is considered equivalent to Literal[True] | AlwaysFalsy#15784
AlexWaygood wants to merge 5 commits intomainfrom
alex/truthy-unions-7

Conversation

@AlexWaygood
Copy link
Member

Summary

This PR is yet another alternative to #15738 and #15773.

I'll writeup a fuller PR summary once I've seen the benchmark results...

Test Plan

@AlexWaygood AlexWaygood added the ty Multi-file analysis & type inference label Jan 28, 2025
@AlexWaygood AlexWaygood force-pushed the alex/truthy-unions-7 branch 2 times, most recently from d7082e4 to e4a7142 Compare January 28, 2025 14:01
@MichaReiser
Copy link
Member

@AlexWaygood is this PR (and the other once mentioned in the summary) still something you plan to work on or can we close the PRs?

@AlexWaygood AlexWaygood changed the title [red-knot] Ensure that bool | AlwaysFalsy is considered equivalent to Literal[True] | AlwaysFalsy [ty] Ensure that bool | AlwaysFalsy is considered equivalent to Literal[True] | AlwaysFalsy Jan 14, 2026
@AlexWaygood
Copy link
Member Author

very merge-conflicted

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

ty Multi-file analysis & type inference

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants