#7167: Make it a warning (not error) to hide an import that isn't exported
---------------------------------+------------------------------------------
Reporter: simonpj | Owner: pcapriotti
Type: bug | Status: merge
Priority: highest | Milestone: 7.6.1
Component: Compiler | Version: 7.4.2
Keywords: | Os: Unknown/Multiple
Architecture: Unknown/Multiple | Failure: None/Unknown
Difficulty: Unknown | Testcase: rename/should_compile/T7167
Blockedby: | Blocking:
Related: |
---------------------------------+------------------------------------------
Changes (by pcapriotti):
* status: new => merge
* testcase: => rename/should_compile/T7167
Comment:
Documentation patch here:
{{{
commit 4eb02c17fc814275a4294afe5c9f38eff8c6a489
Author: Paolo Capriotti <[email protected]>
Date: Sat Aug 25 20:33:36 2012 +0100
Update documentation for -fwarn-dodgy-imports.
}}}
The bug in data family imports mentioned in the commit above is as
follows. Given a module DodgyA:
{{{
{-# LANGUAGE TypeFamilies #-}
module DodgyA(C(..), X(..)) where
class C a where
data X a
instance C Int where
data X Int = X1 Bool
}}}
the following import triggered a "dodgy import" warning:
{{{
import DodgyA (X(..))
}}}
even though the `X1` constructor is exported. This has been fixed by the
refactoring, and is now checked by the testcase
`rename/should_compile/dodgy`.
--
Ticket URL: <http://hackage.haskell.org/trac/ghc/ticket/7167#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
