Skip to content
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.

Sign up for GitHub

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

Jump to bottom

Make apply_type_nothrow robust against TypeVars in upper bounds #49863

Merged
merged 2 commits into from
May 19, 2023
Merged

Make apply_type_nothrow robust against TypeVars in upper bounds #49863

merged 2 commits into from
May 19, 2023

Commits on May 17, 2023

  1. Make apply_type_nothrow robust agaist TypeVars in upper bounds 

    For types like `Foo{S, T<:S}`, `apply_type_nothrow` could in some
situations check whether the argument is a subtype of the upper bound of
`T`, i.e. `S`, but subtyping agaist a plain `TypeVar` would fail.
Instead return `false` in this case.

Fixes #49785.
    @martinholters
    martinholters committed May 17, 2023
    Configuration menu
    Copy the full SHA
    4bb4410 View commit details
    Browse the repository at this point in the history

Commits on May 18, 2023

  1. Merge branch 'master' into mh/fix-49785

    @KristofferC
    KristofferC authored May 18, 2023
    Configuration menu
    Copy the full SHA
    4e502c9 View commit details
    Browse the repository at this point in the history