I agree with Richard as well on this point. The error messages GHC reports can be practically incomprehensible and even misleading when PolyKinds is accidentally turned off in a module that imports and attempts to use poly-kinded things. I could probably drum up an example if people want (I've run into this problem several times, but don't have one immediately on hand.) If it were just switched on by default, I'd feel a lot better about the extension, because I wouldn't have to worry that consumers of any poly-kinded things I wrote had to be aware of these stumbling blocks. Of course, if GHC could get better at suggesting that users should turn PolyKinds on in the cases where it's an issue, that would also be great, but I'm not quite sure how to approach that either. - Cale On Thu, 3 Dec 2020 at 12:48, Joachim Breitner <mail@joachim-breitner.de> wrote:
Hi,
Am Donnerstag, den 03.12.2020, 16:40 +0000 schrieb Richard Eisenberg:
Vote for PolyKinds!
convinced.
Cheers, Joachim -- Joachim Breitner mail@joachim-breitner.de http://www.joachim-breitner.de/
_______________________________________________ ghc-steering-committee mailing list ghc-steering-committee@haskell.org https://mail.haskell.org/cgi-bin/mailman/listinfo/ghc-steering-committee