-
Notifications
You must be signed in to change notification settings - Fork 4.1k
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
Don't let inapplicable members participate in ORPA filtering #75878
Conversation
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.
LGTM (commit 1)
@@ -36,6 +36,7 @@ public bool HasValue | |||
get { return this.Kind != OperatorAnalysisResultKind.Undefined; } | |||
} | |||
|
|||
bool IMemberResolutionResultWithPriority<MethodSymbol>.IsApplicable => IsValid; |
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.
nit: consider renaming existing IsValid
property to IsApplicable
instead. There's not much benefit of having two names for the same thing.
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.
I'd rather keep this scoped. If you want to come back with a refactoring of this I would be happy to review, but I don't want to conflate it with this change.
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.
LGTM Thanks (iteration 1)
Fixes #75871.