#5978: Type error in one function causes wrong type error report in another
function in the presence of functionally dependent types
----------------------------------------+-----------------------------------
Reporter: Lemming | Owner:
Type: bug | Status: new
Priority: normal | Milestone:
Component: Compiler (Type checker) | Version: 7.4.1
Keywords: | Os: Unknown/Multiple
Architecture: Unknown/Multiple | Failure: GHC rejects valid
program
Difficulty: Unknown | Testcase:
Blockedby: | Blocking:
Related: |
----------------------------------------+-----------------------------------
Comment(by Lemming):
Replying to [comment:5 simonpj]:
> I would certainly give type families a try, yes. I'd be interested to
hear how it goes.
I have converted some of my code to type families. Unfortunately, since I
depend on the llvm package, the code is now quite inconsistent, because
llvm uses a lot of functional dependencies and it uses in turn the type-
level package that requires even more functional dependencies. Thus for
now I cannot get rid of the problematic code. My hope is that we can
remove all of these functional dependencies when the type level naturals
(#4385) become part of GHC HEAD.
--
Ticket URL: <http://hackage.haskell.org/trac/ghc/ticket/5978#comment:6>
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
