#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 malcolm.wallace@…):
I can see no case in which a shared module abbreviation could ever lead to
a program doing the wrong thing. If there is a genuine ambiguity about
the referent of an identifier, it will already be reported as an error.
This warning request seems to be about avoiding future compile errors in
this module, due to changes in other modules. But if you are refactoring
code in other modules, you should always at least expect the possibility
of consequent breakage in the modules that import them - that is part of
the joy of static checking. It seems just as likely to me that the future
refactoring could *erroneously* introduce a clashing identifier, as that
the clashing identifier would be deliberate.
--
Ticket URL: <http://hackage.haskell.org/trac/ghc/ticket/4980#comment:4>
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
