Skip to content

Conversation

Evangelink
Copy link
Contributor

Ensure that IEquatable<T> targets nullable type and update related implementation.

Related Issue

Follow-up of #2765

@arturcic arturcic requested review from arturcic and asbjornu July 26, 2021 11:08
Copy link
Member

@asbjornu asbjornu left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Can you please provide a bit more context and information regarding this change? I hoped we would get fewer ? in the codebase going forward, not more?

@Evangelink
Copy link
Contributor Author

I just assumed that as we were doing null checks in the equals, it was better to explicitly allow nulls but I understand your point. We can probably close the PR.

@asbjornu
Copy link
Member

Ok, I see. I suppose it's difficult to ensure these types aren't null earlier in the codebase?

@Evangelink
Copy link
Contributor Author

At this point yes. I assume/hope it will be easier after a couple of null-check iterations :)

@asbjornu
Copy link
Member

Indeed, let's merge this then. Can you please rebase and resolve conflicts?

@Evangelink
Copy link
Contributor Author

@asbjornu Done.

@asbjornu asbjornu merged commit 67abe09 into GitTools:main Jul 31, 2021
@asbjornu asbjornu added this to the 5.x milestone Jul 31, 2021
@mergify
Copy link
Contributor

mergify bot commented Jul 31, 2021

Thank you @Evangelink for your contribution!

@arturcic arturcic modified the milestones: 5.x, 5.6.12 Aug 14, 2021
@arturcic
Copy link
Member

🎉 This issue has been resolved in version 5.7.0 🎉
The release is available on:

Your GitReleaseManager bot 📦🚀

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants