| Cc: glasgow-haskell-users@haskell.org
| Subject: Re: build failures when hiding non-visible imports
|
| On 21 August 2012 07:36, John Lato wrote:
| >> From: Brandon Allbery
| >>
| >> On Sat, Aug 18, 2012 at 9:10 PM, Carter Schonwald <
| >> carter.schonw...@gmail.com> w
On 21 August 2012 07:36, John Lato wrote:
>> From: Brandon Allbery
>>
>> On Sat, Aug 18, 2012 at 9:10 PM, Carter Schonwald <
>> carter.schonw...@gmail.com> wrote:
>>
>>> meaning: flags for treating it as a warning vs as an error? (pardon, i'm
>>> over thinking ambiguity in phrasing).
>>> if that
> From: Brandon Allbery
>
> On Sat, Aug 18, 2012 at 9:10 PM, Carter Schonwald <
> carter.schonw...@gmail.com> wrote:
>
>> meaning: flags for treating it as a warning vs as an error? (pardon, i'm
>> over thinking ambiguity in phrasing).
>> if thats the desired difference, that sounds good to me!
>
On 17/08/2012 11:18, Simon Peyton-Jones wrote:
> | 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 opinion
On Sat, Aug 18, 2012 at 9:10 PM, Carter Schonwald <
carter.schonw...@gmail.com> wrote:
> meaning: flags for treating it as a warning vs as an error? (pardon, i'm
> over thinking ambiguity in phrasing).
> if thats the desired difference, that sounds good to me!
>
I would expect it means that, hav
Peter Aldridge
Engineering Operations Manager
Boeing Aerostructures Australia
Phone: +61 425 818 455
From: Carter Schonwald [mailto:carter.schonw...@gmail.com]
Sent: Sunday, August 19, 2012 11:10 AM
To: Dan Burton
Cc: glasgow-haskell-users@haskell.org
Subject: Re: build failures when hiding
meaning: flags for treating it as a warning vs as an error? (pardon, i'm
over thinking ambiguity in phrasing).
if thats the desired difference, that sounds good to me!
-Carter
On Sat, Aug 18, 2012 at 5:29 PM, Dan Burton wrote:
> Sounds reasonable. We might want flags to go with it for silencing
Sounds reasonable. We might want flags to go with it for silencing or
enabling that particular warning.
-- Dan Burton
___
Glasgow-haskell-users mailing list
Glasgow-haskell-users@haskell.org
http://www.haskell.org/mailman/listinfo/glasgow-haskell-users
Simon Peyton-Jones wrote:
> | 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?
+1 for a warning
sage-
| From: glasgow-haskell-users-boun...@haskell.org [mailto:glasgow-
| haskell-users-boun...@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
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 ex
11 matches
Mail list logo
