Equals compares collections last
Before this PR
When evaluating equals(Object), collection types are compared before other relative cheaper fields.
After this PR
==COMMIT_MSG== Equals compares collections last ==COMMIT_MSG==
Possible downsides?
Generate changelog in changelog/@unreleased
changelog/@unreleasedType
See change types. Select one:
- [ ] Feature
- [ ] Improvement
- [ ] Fix
- [ ] Break
- [ ] Deprecation
- [ ] Manual task
- [ ] Migration
Description
Check the box to generate changelog(s)
- [ ] Generate changelog entry
Right now this is still just a raw WIP I wanted to brain dump as I was digging through a few JFR and saw some conjure types equals methods evaluating java.util.Collections$UnmodifiableSet.equals(Object).
There are some places where we might want to just manually reorder fields in yaml, but was thinking we could defer collection comparison to short-circuit in case of mismatches.
