in newer versions of ghc, client code of a module that uses constraint kinds gets constraint kinds enabled.this is to make it pleasant to use constraint kinds in libraries.this is deliberate feature :)On Thu, May 4, 2017 at 6:46 PM, Brandon Allbery <allbery.b@gmail.com> wrote:______________________________On Thu, May 4, 2017 at 6:42 PM, Wolfgang Jeltsch <g9ks157k@acme.softbase.org> wrote:In my previous e-mail, I showed some code that uses the Constraint kind.
I forgot to enable the ConstraintKinds extension though, but GHC 8.0.1
did not complain. Is this a bug?I think it's a known side effect of * being conflated with Constraint, a problem that is actively being worked on ( https://ghc.haskell.org/trac/ghc/ticket/11715 ).--brandon s allbery kf8nh sine nomine associatesunix, openafs, kerberos, infrastructure, xmonad http://sinenomine.net_________________
Glasgow-haskell-users mailing list
Glasgow-haskell-users@haskell.org
http://mail.haskell.org/cgi-bin/mailman/listinfo/glasgow-has kell-users