[m-dev.] another interface file?

Zoltan Somogyi zs at csse.unimelb.edu.au
Thu Jun 4 18:11:23 AEST 2009

On 04-Jun-2009, Julien Fischer <juliensf at csse.unimelb.edu.au> wrote:
> One alternative would be to always hoist abstract equivalance type
> definitions (plus any supporting definitions) into the implementation
> sections of the existing interface files.  Obviously, this will affect 
> separate
> compilation to some extent.  On the upside, it would also make detecting
> overlapping type class instances easier.

Any such forced export should be ignored by the compiler until *after*
the front end. We do not yet have a mechanism for this.

mercury-developers mailing list
Post messages to:       mercury-developers at csse.unimelb.edu.au
Administrative Queries: owner-mercury-developers at csse.unimelb.edu.au
Subscriptions:          mercury-developers-request at csse.unimelb.edu.au

More information about the developers mailing list