-
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
Test IterableSubject methods on objects that don't implement hashCode() #176
Comments
By "don't implement |
…elements don't implement hashCode() (e.g., ProtoBuf's MessageSet!) See []where the user can't use .containsExactlyElementsIn(). This at least partially addresses #176 ------------- Created by MOE: http://code.google.com/p/moe-java MOE_MIGRATED_REVID=89605122
…elements don't implement hashCode() (e.g., ProtoBuf's MessageSet!) This at least partially addresses #176 ------------- Created by MOE: http://code.google.com/p/moe-java MOE_MIGRATED_REVID=89605122
…elements don't implement hashCode() (e.g., ProtoBuf's MessageSet!) This at least partially addresses #176 ------------- Created by MOE: http://code.google.com/p/moe-java MOE_MIGRATED_REVID=89605122
We just got a report internally that failing tests still call
I wonder if we could get away with using an [Update: I did that.] |
…hrow an exception. We'd rather they didn't, but let's do what we can... :( (progress toward #176) RELNOTES=n/a PiperOrigin-RevId: 463138856
…hrow an exception. We'd rather they didn't, but let's do what we can... :( (progress toward #176) RELNOTES=n/a PiperOrigin-RevId: 463143598
Such objects are at least a little evil, but they exist in one or two Google-internal projects. If we currently support this, then we should continue to do so, or at least we should have a test that lets us know that we're breaking it so that we don't do so by mistake.
The text was updated successfully, but these errors were encountered: