[GHC] #8043: Feature Request : Qualified module exports
GHC
ghc-devs at haskell.org
Mon Jul 8 05:52:37 CEST 2013
#8043: Feature Request : Qualified module exports
------------------------------------+-------------------------------------
Reporter: erikd | Owner:
Type: bug | Status: new
Priority: normal | Milestone:
Component: Compiler | Version: 7.7
Keywords: | Operating System: Unknown/Multiple
Architecture: Unknown/Multiple | Type of failure: Other
Difficulty: Unknown | Test Case:
Blocked By: | Blocking:
Related Tickets: |
------------------------------------+-------------------------------------
I quite like the practice of using `-XNoImplicitPrelude` and then defining
my own (often per-project) Prelude doing things like:
{{{
module MyProject.Prelude
( module P
)
import Data.Text as P (Text)
import Prelude as P hiding (head, init, tail, last)
}}}
As an extension to the above idea, I would like to add qualified module
exports defined so that I can do this:
{{{
module MyProject.Prelude
( module P
, qualified module T
)
import Data.Text as P (Text)
import Prelude as P hiding (head, init, tail, last)
import qualified Data.Text as T
}}}
so that any file which imports `MyProject.Prelude` will then have all the
identifiers that they would normally get if they did:
{{{
import qualified Data.Text as T
}}}
Is this something that would have to go through the Haskell Next
procedure? If so, how does one get that kicked off?
--
Ticket URL: <http://ghc.haskell.org/trac/ghc/ticket/8043>
GHC <http://www.haskell.org/ghc/>
The Glasgow Haskell Compiler
More information about the ghc-tickets
mailing list