-
-
Notifications
You must be signed in to change notification settings - Fork 2.9k
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
Unwrap type[Union[...]]
when solving typevar constraints
#18266
base: master
Are you sure you want to change the base?
Unwrap type[Union[...]]
when solving typevar constraints
#18266
Conversation
This comment has been minimized.
This comment has been minimized.
Primer diff is fine, it was a false positive. |
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.
Thanks for the PR! I had a few comments but looks good overall.
This comment has been minimized.
This comment has been minimized.
Hm, and this new diff is weird. I'll try to figure out the reason for the |
… be unwrapped, so type should be restored when passing it further
The upstream code has changed since, but I checked the previous version locally and confirmed the bug is gone. This should be ready for another review now. |
Diff from mypy_primer, showing the effect of this PR on open source code: Tanjun (https://github.com/FasterSpeeding/Tanjun)
- tanjun/annotations.py:1064: error: Incompatible return value type (got "object", expected "User | Role | Snowflake | _T") [return-value]
|
Closes #18265, closes #12115.
type[A | B]
is internally represented astype[A] | type[B]
, and this causes problems for a typevar solver. Prevent using meet in such cases by unwrapingtype[...]
if both sides have such shape.