[m-rev.] for review: list__sort_and_remove_equivs/3

[Ralph Becket]

Mark Brown, Thursday,  5 September 2002:
> 
> Actually, I've just thought of a potential problem with this change.  The
> problem is that if list__sort is not stable, then the output of the new
> predicate is not well defined (that is, there would be more than one
> solution that fits the specification).  Is list__sort meant to be stable?

It would be a desirable property - if it matters for a given application
then it would be good to just use the standard sort function; if it
doesn't then you don't care either way.

- Ralph
--------------------------------------------------------------------------
mercury-reviews mailing list
post:  mercury-reviews at cs.mu.oz.au
administrative address: owner-mercury-reviews at cs.mu.oz.au
unsubscribe: Address: mercury-reviews-request at cs.mu.oz.au Message: unsubscribe
subscribe:   Address: mercury-reviews-request at cs.mu.oz.au Message: subscribe
--------------------------------------------------------------------------