Your point is taken, but again, I really don't want to micromanage auto-generated code. The consequence for a hash collision is, generally, pretty small (because we're still checking `.equals` after that). If we have reason to believe that hash collisions are a major performance problem, we should tackle the issue more comprehensively. If we do so, I would much rather tackle that as its own thing rather than making it a rider on this change.

> I would +1 using `Objects.hash`

That would mean dropping support for Java 6, and I don't think we want to do that right now.