-
Notifications
You must be signed in to change notification settings - Fork 255
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
AreEqual/AreNotEqual XML documentation is wrong #1551
Comments
Hi @cremor, You are absolutely right! I just had a look and it doesn't seem to be a regression and all versions always worked as-is. I think the first implementation was containing only Given that and no-one ever complained about this logical equality rather than "type" equality, I would simply update the doc. Is it something you would be willing to contribute or shall we do it on our side? |
👍
I don't think that I'll have time for this in the near future, sorry. |
No worries! Thanks for taking the time to reply! @engyebrahim, I am adding that to your backlog. |
Many of the AreEqual/AreNotEqual overloads contain this text in their XML documentation:
This is wrong.
To see this, run the following tests. Both will have results that do not match the expectation from the XML documentation.
AB#1726907
The text was updated successfully, but these errors were encountered: