#11971: Unify error messages that suggest enabling extensions -------------------------------------+------------------------------------- Reporter: cocreature | Owner: Type: feature request | Status: new Priority: low | Milestone: Component: Compiler | Version: 7.10.3 Resolution: | Keywords: Operating System: Unknown/Multiple | Architecture: | Unknown/Multiple Type of failure: None/Unknown | Test Case: Blocked By: | Blocking: Related Tickets: | Differential Rev(s): Wiki Page: | -------------------------------------+------------------------------------- Description changed by cocreature: @@ -3,2 +3,2 @@ - Here are just a few examples (I’ll do a longer search if we come to a - consensus) + Here are just a few examples (I’ll do a longer search if there is a + consensus to move forward with this ticket) New description: The error messages that suggest to enable some extension currently have a lot of slightly different forms: Here are just a few examples (I’ll do a longer search if there is a consensus to move forward with this ticket) - Did you mean to enable _? - Did you mean to use _? - Perhaps you meant to use _? - Perhaps you intended to use _? These error messages are parsed by haskell-mode (and maybe other tooling as well) which is quite hard since they have so many different forms. I propose to change all of those to “Did you mean to enable _?” since that I prefer enable over use here, but I don’t have any strong feelings towards the exact message as long as it’s consistent. So if the majority prefers something else I’m fine with that. -- -- Ticket URL: http://ghc.haskell.org/trac/ghc/ticket/11971#comment:1 GHC http://www.haskell.org/ghc/ The Glasgow Haskell Compiler