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

Include a field's interface in equality and hashing. #51

Merged
merged 1 commit into from
Aug 31, 2018
Merged

Conversation

jamadden
Copy link
Member

Fixes #40

There will be test conflicts with #50. Once either of them is merged I will fix the test conflicts and expand the usage of the EqualityTestsMixin to cover the rest of the fields in the remaining PR.

@jamadden jamadden merged commit ff8f729 into master Aug 31, 2018
@jamadden jamadden deleted the issue40 branch August 31, 2018 17:11
@jamadden
Copy link
Member Author

Thanks!

jamadden added a commit that referenced this pull request Sep 1, 2018
Fixes #18

Some other vocabulary fixes while I was in there:

- Make TreeVocubalary.fromDict only actually assign titles when a
  title is given. This makes it consistent with
  SimpleVocubalary.fromItems().

- Give equality and hash methods to SimpleTerm and SimpleVocubalary.
  This was a confusing stumbling block in the implementation of #51.
jamadden added a commit that referenced this pull request Sep 1, 2018
Fixes #18

Some other vocabulary fixes while I was in there:

- Make TreeVocubalary.fromDict only actually assign titles when a
  title is given. This makes it consistent with
  SimpleVocubalary.fromItems().

- Give equality and hash methods to SimpleTerm and SimpleVocubalary.
  This was a confusing stumbling block in the implementation of #51.
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.

Should Field objects include their owning interface in equality/hashing?
2 participants