While we appreciate comments from our users, please follow our posting guidelines. Have you tried the Cyotek Forums for support from Cyotek and the community?
Styling with Markdown is supported
06 April 2016 Reply
May I suggest that you exit the loop as soon as possible when results == false as there is absolutely no need to continue since the answer is already found and more importantly because we're using "costly" algorithm (reflection)?
You're right of course, but actually I did that deliberately. This was because I wrote this code for use in testing (quite often I don't add IEquatable or IComparable to my classes) and I remember specifically getting really annoyed when tests would fail, I'd fix the first mismatch, but then I'd have to wait for them to run again to get the next. By not breaking out of that loop early I could get all mismatches at once and then fix them at once - I was never worried about the inefficiency as it was "just" testing.