Before we introduced a Tuple type for fixed-size array, we used to enforce the correct size of object members of type array using some calls to assertMemberLength() in the constructor.
In between, a lot of such arrays were migrated into Tuples.
Therefore, passing an array or a Tuple of the wrong size would be detected at compile-time and therefore the use of assertMemberLength() is not needed anymore.
One might argue that maintaining assertMemberLength() use would detect abuse of type casting like 'array as Tuple<>' though.
Before we introduced a Tuple type for fixed-size array, we used to enforce the correct size of object members of type array using some calls to assertMemberLength() in the constructor.
In between, a lot of such arrays were migrated into Tuples.
Therefore, passing an array or a Tuple of the wrong size would be detected at compile-time and therefore the use of assertMemberLength() is not needed anymore.
One might argue that maintaining assertMemberLength() use would detect abuse of type casting like 'array as Tuple<>' though.