[m-rev.] for review: allow arbitrary types in class constraints

[Zoltan Somogyi]

On 12-Apr-2002, David Jeffery <dgj at missioncriticalit.com> wrote:
> (The problem being that the type_info_locn type has no way
> of specifying that type-info for T can be found inside something
> which is inside the typeclass-info for c(f(T))). It should be possible 
> to make it work, but I suspect it won't "just" work (in all cases).

On the other hand, redesigning the data structures for typeclass_infos
and base_typeclass_infos is one of things on my plate. At the moment,
they are the only builtin data types that cannot be deconstructed, printed out,
compared, etc.

So far, I have only thought about what the new data structures should look
like; I haven't started coding. (I do know I want two forms for each data
structure, once defined in C and one in Mercury.) If we need to stop
imposing some of the constraints we used to impose, I can take that into
account.

Zoltan.
--------------------------------------------------------------------------
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
--------------------------------------------------------------------------