[m-dev.] more unnecessary recompilation problems

Simon Taylor stayl at cs.mu.OZ.AU
Tue Feb 10 18:27:14 AEDT 2004

On 10-Feb-2004, Fergus Henderson <fjh at cs.mu.OZ.AU> wrote:
> Every time I add a new ":- import_module" declaration to the *implementation*
> section of module, Mmake decides to recompile the world.
> This problems seems to have been introduced by Simon's equivalence type
> changes.
> If I understand things correctly, the import_module declarations in
> the implementation section are needed in order to resolve references in
> abstract equivalence types.  But in this case, the module doesn't
> HAVE any abstract equivalence types -- it has some equivalence types,
> but they are private, not abstract.  Why do they get put in the .int
> or .int2 files?

Lack of time.  We should only include types which are (indirectly)
used by exported types.

> Even in cases where there are abstract equivalences types, the types on
> the right-hand sides of those are all fully-qualified at this point.
> So we know exactly which modules they refer to.  Wouldn't it be better
> to only import those modules which are actually referred to?


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

More information about the developers mailing list