Strange curried case class constructor behaviour

That does indeed make a lot of sense. Just wondered about this, due to some work I am doing to a related topic and I wasn’t able to access the fields from outside. I did some digging with reflections and found this. On the first look it looked like something unintended, but when you look at it with equality in mind, the behaviour seems sensible.