#4980: Warning about module abbreviation clashes
---------------------------------+------------------------------------------
Reporter: Lemming | Owner:
Type: feature request | Status: new
Priority: normal | Milestone: 7.4.1
Component: Compiler | Version: 7.0.1
Keywords: | Testcase:
Blockedby: | Difficulty:
Os: Unknown/Multiple | Blocking:
Architecture: Unknown/Multiple | Failure: None/Unknown
---------------------------------+------------------------------------------
Comment(by Lemming):
Replying to [comment:4 malcolm.wallace@…]:
> This warning request seems to be about avoiding future compile errors in
this module, due to changes in other modules.
Right, this warning is intended to avoid compilation errors if something
in the imported modules is added. This is especially important if the
imported modules are from another package. If I want to import a PVP
compliant package X with
{{{
Build-Depends: X >= A.B.C && < A.(B+1)
}}}
then I have to make sure that additions to the APIs of the imported
modules do not lead to compilation errors.
The goal is the same as in #4977.
Btw. Modula forbids clashing module abbreviations and only allows
unqualified import with explicit enumeration and qualified import (as in
#4977) in order to protect against compilation failure if something is
added to imported modules.
--
Ticket URL: <http://hackage.haskell.org/trac/ghc/ticket/4980#comment:5>
GHC <http://www.haskell.org/ghc/>
The Glasgow Haskell Compiler
_______________________________________________
Glasgow-haskell-bugs mailing list
[email protected]
http://www.haskell.org/mailman/listinfo/glasgow-haskell-bugs
