-
Notifications
You must be signed in to change notification settings - Fork 4.8k
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
Remove stale TODO-NULLABLE comments from code #44136
Conversation
50f7789
to
92a03cf
Compare
92a03cf
to
e234898
Compare
throw new Exception(SR.Diagnostic_InternalExceptionMessage); | ||
} | ||
return MemberType.GetHashCode() ^ _accessors[0]!.GetHashCode(); // TODO-NULLABLE: Indexer nullability tracked (https://github.com/dotnet/roslyn/issues/34644) | ||
return MemberType.GetHashCode() ^ accessor.GetHashCode(); |
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: should this use hash code combiner? cc: @GrabYourPitchforks
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.
HashCodeCombiner
is good for things that don't have a great distribution already. One example is a record type where the user is responsible for providing most of the fields, which is likely to see many of the values clustered around the same set of hash codes. Since this hash code calculation routine is using reflection and other runtime objects, there's not as much concern about clustering, since these objects already have good distribution.
src/libraries/System.Drawing.Common/src/System/Drawing/Printing/PrintingServices.Unix.cs
Show resolved
Hide resolved
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, one question about product change
cc: @krwq, @jeffhandley