Skip to content
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

Added hashCode and equals implementations #358

Open
wants to merge 1 commit into
base: dev
Choose a base branch
from
Open

Added hashCode and equals implementations #358

wants to merge 1 commit into from

Conversation

farazdurrani
Copy link

@farazdurrani farazdurrani commented May 5, 2019

Added hashCode and equals implementations so adding a duplicate to Set stops it from adding.

This checklist is used to make sure that common guidelines for a pull request are followed.

  • I have read the contribution guidelines.
  • Title of the pull request is clear and informative.
  • There are a small number of commits, each of which have an informative message. This means that previously merged commits do not appear in the history of the PR.
  • The pull request does not introduce breaking changes (unless a major version change occurs in the assembly and module).
  • If applicable, the public code is properly documented.
  • Pull request includes test coverage for the included changes.
  • The code builds without any errors.

Added hashCode and equals implementations so adding a duplicate to Set stops it from adding.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant