Closed m-ringler closed 3 years ago
Thank you for your bug report! I've created some unit tests to repro it and was able to fix it without requiring awkward code in the derived type.
This will be fixed in version 6.1.0
. If you would like the fix now, you can upgrade to version 6.1.0-pre03
which should be published shortly.
That really is much better. Thanks for the fix (and a very useful library).
In the example code for
EquatableBase<T>
declare a DefaultComparer property in the derived type to make sure that the static constructor has run. This will prevent users from getting null when using DerivedType.DefaultComparer (as I have repeatedly).