-
-
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
Merge lookup_fully_qualified and lookup_fully_qualified_or_none #11205
Merge lookup_fully_qualified and lookup_fully_qualified_or_none #11205
Conversation
This comment has been minimized.
This comment has been minimized.
@hauntsaninja Should we use |
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 change and shorter name seem fine to me. It might be worth doing lookup_fully_qualified_or_none = lookup_fully_qualified
in SemanticAnalyzer
, just to reduce churn / mypy versioning headaches for plugins.
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 updates! The PR looks nice and tidy now. Sorry for the extra iterations, but I think that the end result makes it worth it.
Description
Partially solves #4157
SemanticAnalyzerCoreInterface.lookup_fully_qualified
seems redundant