I don’t think it’s worth it
oh right that thing
brb
where can I put that in
should be in the resharper settings for that project
tried, it came up with them, and then they were gone
gotit
properties window of the .Portable project
UGH
the first fix it suggests is “turn on C#6 support"
and there’s no other fix
...called every time and it takes about 4 times longer than comparing the strings themselves
So, actually it is more costly and doesnt add any performance when used on few instances.
So, maybe we need more than one hashcode? Could we have a fail-fast-hash that only uses few properties?
oh wait like that
hmm
but that makes things more complicated
let’s first measure things
Just saying, because GetHashCode itself is already trying to be an optimization
like if the event message is different.. there’s no need to do a full hashcode
Which would only happen rarely
Let's test
it does save calculating them a lot though
I wonder if System.String save the hashcode internally after requesting