| Would it be reasonable to change ghc's behavior to treat this | (ie an 'import' statement that hides something that isn't exported) as a | warning instead of an error? Yes, that would be easy if it's what everyone wants. Any other opinions? Simon | -----Original Message----- | From: glasgow-haskell-users-bounces@haskell.org [mailto:glasgow- | haskell-users-bounces@haskell.org] On Behalf Of John Lato | Sent: 17 August 2012 02:13 | To: glasgow-haskell-users@haskell.org | Subject: build failures when hiding non-visible imports | | Hello, | | One of the issues I've noticed with ghc-7.6 is that a number of | packages fail due to problematic import statements. For example, any | module which uses | | > import Prelude hiding (catch) | | now fails to build with the error | | Module `Prelude' does not export `catch' | | Of course fixing this example is relatively straightforward, but that | isn't always the case. | | Would it be reasonable to change ghc's behavior to treat this as a | warning instead of an error? | | Cheers, | John L. | | _______________________________________________ | Glasgow-haskell-users mailing list | Glasgow-haskell-users@haskell.org | http://www.haskell.org/mailman/listinfo/glasgow-haskell-users