This has been discussed before (search the issues).
Regarding the tuple library you suggest: I understand that the way it
was implemented resulted in maximum code reuse, but
"tuple.rest.rest.rest.rest.rest.rest.rest.rest.rest.first" looks...
not healthy.
And honestly, I have my own tuple classes, and I rarely need anything
larger than Pair. For bigger things it is more readable to create a
proper class.
> --
> Google Collections Library - users list
>
http://groups.google.com/group/google-collections-dev?hl=en
>
> To unsubscribe, send email to:
>
google-collections...@googlegroups.com
--
Johan Van den Neste