That sounds like a need for named and default constructor parameters. With the two of those, you can mix-and-match whatever values you want, with non-defaulted ones being required. And since the parameters are named, they self-document at the usage site.
Re:The Current State of Java Value Types
by kjeetgill on Thursday June 21, 2018 @08:38PM
(#17370357)
I know it's not quite what you're asking for but Java's annotations allow for pretty reasonable and compose-able preprocessors to implement things like this. Checkout lombok's @Builder annotation https://projectlombok.org/features/Builder
The options we have right now are bad: the long constructor arguments are too verbose, the setters are causing non-immutability and builders are worst due to lack of discoverability and standards.