🚀 go-pugleaf

In article <1992Aug26.141437.8465@swift.cs.tcd.ie> butrfeld@swift.cs.tcd.ie writes:

> In a language called Sticks&Stones, based loosely on ML, that I have
> used, the following equality always held:

> (a,(b,c)) = (a,b,c)

> In other words a triple is simply a pair whose second item is a pair.
> Note that ((a,b),c) is not a triple.

It sounds like that language didn't allow triples at all, only pairs.
It's certainly possible to do that, but that would certainly be less
convenient in other ways.

For example, in ML a pair is a special case of a more general record
type that consists of name-value pairs known and checked at compile
time.  A pair is just a record whose components are named 1 and 2;
a triple is a record with components named 1, 2, and 3, and so on.
I don't see how to allow pairs and not triples with that kind of
unified design, and that unification is truly elegant and makes
all sorts of other things easier to understand.
-- 
				--Andrew Koenig
				  ark@europa.att.com