Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
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
Improve S1244: Add message to use "IsNaN" instead of "== double.NaN" #6664
Improve S1244: Add message to use "IsNaN" instead of "== double.NaN" #6664
Changes from 7 commits
0bad0c7
c5f1e86
d3ffcb3
24d3a1d
af5e0a2
eda6878
ed5aced
16178b5
0c0ae6a
File filter
Filter by extension
Conversations
Jump to
There are no files selected for viewing
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.
Doesn't this miss the BuiltinOperator?
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 rule S4050 only focuses on methods that are user-defined.
This is the reason why
KnownMethods.IsOperatorXXX
originally had the constraintMethodKind: MethodKind.UserDefinedOperator
.By partially relaxing that constraint (which is now
MethodKind: MethodKind.BuiltinOperator or MethodKind.UserDefinedOperator)
, we could reuseKnownMethods.IsOperatorXXX
elsewhere.That, however, required adding an additional check here, to ensure operators defined at higher level in the class hierarchy would not be taken into account.
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.
Okay. Got it now. You may still use the pattern syntax instead of the
when
if you like.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.
As I don't have an opinion on whether the
!=
is better or worse than: not
in this specific context, I've welcomed your suggestion and made the change.I am curious though, about why would recommend the pattern-matching version over the classic way.
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.
Fairly simple:
when
is the fallback whenever pattern matching isn't possible.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 agree that a pattern matching is better than the ugly workaround we did