#5306: Data family constructor imports broken
------------------------------------------+---------------------------------
Reporter: reinerp | Owner: simonpj
Type: bug | Status: closed
Priority: normal | Milestone: 7.4.1
Component: Compiler | Version: 7.0.3
Resolution: fixed | Keywords: type families
Testcase: rename/should_compile/T5306 | Blockedby:
Difficulty: | Os: Unknown/Multiple
Blocking: | Architecture: Unknown/Multiple
Failure: GHC rejects valid program |
------------------------------------------+---------------------------------
Comment(by simonpj):
I backtracked on a rather ad-hoc change I made in the above patch, but
didn't draw attention to. Here's the patch that undoes the hack:
{{{
commit f5c0851a72f7a9cb8a7349eec7a6d4262be7295d
Author: Simon Peyton Jones <[email protected]>
Date: Fri Sep 2 17:34:00 2011 +0100
Backtrack on the wierd special case of data family exports
I had second thoughts on the "data family export" question.
Rather than add a wierd special case it seems better to be
simple and consistent. So this patch
* Reverts to the simple behaviour:
module M where { ... }
exports only what is defined in M, ie NOT any
imported data families.
See Note [Exports of data families] in RnNames
* Documents this behaviour in the user manual, and clarifies
what was there before.
compiler/rename/RnNames.lhs | 41 +++++------
docs/users_guide/glasgow_exts.xml | 142
+++++++++++++++++++++++--------------
2 files changed, 105 insertions(+), 78 deletions(-)
}}}
--
Ticket URL: <http://hackage.haskell.org/trac/ghc/ticket/5306#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
