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

Recursive data structures in Java API classes #30

Closed
GoogleCodeExporter opened this issue Mar 29, 2015 · 2 comments
Closed

Recursive data structures in Java API classes #30

GoogleCodeExporter opened this issue Mar 29, 2015 · 2 comments

Comments

@GoogleCodeExporter
Copy link

Some Java API classes contain recursive data structures. If you include one of 
these in as a field, EqualsVerifier complains about it, even if the class isn't 
part of the equals/hashCode contract.

You can work around it by adding them to the prefabValues manually. However, 
this isn't very nice. It would be better if EqualsVerifier already contained 
prefabValues for these classes.

Classes for which this applies:
* java.util.Date
* java.util.regex.Pattern
* more?

Original issue reported on code.google.com by [email protected] on 20 Jul 2010 at 11:57

@GoogleCodeExporter
Copy link
Author

* HashMap / HashMap.Entry
* WeakHashMap / WeakHashMap.Entry
* more maps/collections?

Original comment by [email protected] on 23 Jul 2010 at 9:54

  • Added labels: ****
  • Removed labels: ****

@GoogleCodeExporter
Copy link
Author

It's actually become quite a list. Most Map, Queue and Set implementations were 
affected, as well as (Gregorian)Calendar, Locale, Scanner, and several others.

I think I got most of them now.

Original comment by [email protected] on 4 Aug 2010 at 9:12

  • Changed state: Fixed
  • Added labels: ****
  • Removed labels: ****

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

No branches or pull requests

1 participant