So, it's not considered an error if you do something
like
module A ( B(C), ...some other stuff..., B(D) ) where
...
data B = C | D
but C and D is exported. Is the extra flexibility of
allowing duplicates really worth it?
--sigbjorn
----- Original Message -----
From: "Simon Peyton-Jones" <[EMAIL PROTECTED]>
To: "Sigbjorn Finne" <[EMAIL PROTECTED]>; <[EMAIL PROTECTED]>
Sent: Wednesday, September 12, 2001 00:59
Subject: RE: Haskell98 undefinedness
> Yes, it's the same as exporting just B(..) or B(C).
> I guess I should try to make this clearer.
>
> S
>
> | -----Original Message-----
> | From: Sigbjorn Finne [mailto:[EMAIL PROTECTED]]
> | Sent: 11 September 2001 20:31
> | To: [EMAIL PROTECTED]
> | Subject: Haskell98 undefinedness
> |
> |
> | What's the meaning of
> |
> | module A (B, B(..)) where { data B = C };
> |
> | Is or isn't C exported? i.e., the H98 report is silent
> | about what it means to have entity duplicates in
> | an export list, possibly with different 'visibility'
> | modifiers.
> |
> | --sigbjorn
> |
> |
> |
> | _______________________________________________
> | Haskell mailing list
> | [EMAIL PROTECTED] http://www.haskell.org/mailman/listinfo/haskell
> |
_______________________________________________
Haskell mailing list
[EMAIL PROTECTED]
http://www.haskell.org/mailman/listinfo/haskell
