RE: spurious export conflict

| That would be the analysis if the export list were (module M), but
| "If the export list is omitted, all values, types and classes defined
| in the module are exported, _but not those that are imported_."
| There should never be ambiguity or conflicts if the export list is
| omitted.

Stupid me.  GHC currently treats
        module M where ...
as short for
        module M( module M ) where ....

but it isn't any more.  I'd better fix that.

Simon