Change Tuple v1 to fst and v2 to snd about jool HOT 3 CLOSED

I just realized how stupid this was remembering that more tuples exist than just Tuple2 and that would break the consistency, sorry!

from jool.

Thanks for your suggestion, @abueide. When I created jOOλ, I had briefly considered what this library did: https://www.javatuples.org

Unit<A> (1 element)
Pair<A,B> (2 elements)
Triplet<A,B,C> (3 elements)
Quartet<A,B,C,D> (4 elements)

Interestingly enough, they named their tuples without indicating the degree as a number, but then still used (zero based, yuck) accessors, like getValue3(), and, probably as a compromise, didn't number their generic type variables, but named them <A, B, C, D>.

This just to show you there isn't really a very satisfying solution that fits everyone. Much better than tuples in general would be records (with named attributes). If Java had anonymous types like C#, then we would hardly use tuples at all, which are impractical, regardless if the value is called v2 or second or whatever. Because a much bettern name for it would be lastName (for example).

As long as type inference works (with lambdas or var), it would actually be possible to write things like:

Stream.of("a", "b")
    .map(s -> new Object() { String name = s; })
    .forEach(o -> System.out.println(o.name));

But we cannot pass around this type between methods, so the utility is almost zero. We did get first class records with Java 14, though, so I have high hopes that the name of tuple attributes will become irrelevant in the future :)

Cheers,
Lukas

from jool.

@lukaseder Thanks for sharing your insight on the problem, Java 14's records does look promising.

from jool.