It's being used in RenameDetectorTest on line 484. Basically, I needed a way to assert that the modify I started with was the same as the modify I ended up with, even though the modify was split apart and recombined. AssertSame couldn't do that, so I added a .equals and used assertEquals. That being said, since recombined modifys will now have a score associated with them, calling .equals will no longer work. I can remove the method if you wish, or I could keep it an implement hashCode.