[m-dev.] for review: tuples [1]

[Ralph Becket]

> From: Peter Schachte [mailto:schachte at cs.mu.OZ.AU]
> 
> I can only see one disadvantage:  for triples and above, the 
> representation is
> inefficient (and for pairs, the standard pair type is 
> probably fine).  This
> could be fixed by implementing structure inlining of 
> single-constructor types.
> Of course, this would have benefits in many other situations, 
> as well.  Is
> there some reason that this is a more difficult optimization 
> than it would
> seem?

I think you've hit the nail upon the head there.  My personal
feeling is that having efficient, working tuples is of higher
priority than list-style decomposable tuples.

Ralph
--------------------------------------------------------------------------
mercury-developers mailing list
Post messages to:       mercury-developers at cs.mu.oz.au
Administrative Queries: owner-mercury-developers at cs.mu.oz.au
Subscriptions:          mercury-developers-request at cs.mu.oz.au
--------------------------------------------------------------------------