[mercury-users] higher order types + type class constraints

[Fergus Henderson]

On 28-Nov-2000, Michael Day <mikeday at corplink.com.au> wrote:
> 
> > You can't.  In fact you can't pass around polymorphic higher-order
> > terms at all.  Mercury does not directly support "first class polymorphism".
> 
> Is that a limitation that will be removed at some undefined point in the
> future, or just something that people will have to work around?

I think it would be nice to support such things, but the need for it seems
to be quite rare, and the implementation effort required is non-trivial,
so it's a low priority.

If the feature turns out to be commonly needed, or if there is a
particular class of applications for which it is commonly needed,
that would be a good reason to support it.

-- 
Fergus Henderson <fjh at cs.mu.oz.au>  |  "I have always known that the pursuit
                                    |  of excellence is a lethal habit"
WWW: <http://www.cs.mu.oz.au/~fjh>  |     -- the last words of T. S. Garp.
--------------------------------------------------------------------------
mercury-users mailing list
post:  mercury-users at cs.mu.oz.au
administrative address: owner-mercury-users at cs.mu.oz.au
unsubscribe: Address: mercury-users-request at cs.mu.oz.au Message: unsubscribe
subscribe:   Address: mercury-users-request at cs.mu.oz.au Message: subscribe
--------------------------------------------------------------------------