| That would be the analysis if the export list were (module M), but
| "If the export list is omitted, all values, types and classes defined
| in the module are exported, _but not those that are imported_."
| There should never be ambiguity or conflicts if the export list is
| omitted.
Stupid me.
On Mon, Jan 06, 2003 at 05:36:47PM -, Simon Peyton-Jones wrote:
> | GHC reports an export conflict on the following:
> |
> | module M where
> | import List as M
> | sort = "foo"
>
> It's not spurious. Both
>
> M.sort
> and
> Data.List.sort
>
> are in scope under both
| To: [EMAIL PROTECTED]
| Subject: spurious export conflict
|
| GHC reports an export conflict on the following:
|
| module M where
| import List as M
| sort = "foo"
| ___
| Glasgow-haskell-bugs mailing list
| [EMAIL PR
GHC reports an export conflict on the following:
module M where
import List as M
sort = "foo"
___
Glasgow-haskell-bugs mailing list
[EMAIL PROTECTED]
http://www.haskell.org/mailman/listinfo/glasgow-haskell-bugs
