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.

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

(minor) Short circuit call to can_be_type_alias when using PEP 613 #11904

Merged
merged 1 commit into from
Jan 5, 2022

Conversation

hauntsaninja
Copy link
Collaborator

When debugging #11887 I realised can_be_type_alias can do non-trivial
amounts of work. It's unlikely to ever show up on a profile,
but reordering the check means we do less work. Changed the order of
some other checks for consistency.

When debugging python#11887 I realised `can_be_type_alias` can do non-trivial
amounts of work. It's unlikely to ever show up on a profile,
but reordering the check means we do less work. Changed the order of
some other checks for consistency.
@hauntsaninja hauntsaninja merged commit 9c05d3d into python:master Jan 5, 2022
@hauntsaninja hauntsaninja deleted the pep613ref branch January 5, 2022 07:44
tushar-deepsource pushed a commit to DeepSourceCorp/mypy that referenced this pull request Jan 20, 2022
…ython#11904)

When debugging python#11887 I realised `can_be_type_alias` can do non-trivial
amounts of work. It's unlikely to ever show up on a profile,
but reordering the check means we do less work. Changed the order of
some other checks for consistency.

Co-authored-by: hauntsaninja <>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants