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
It's not spurious. Both
M.sort
and
Data.List.sort
are in scope under both names:
sort and M.sort
And that makes it ambiguous according to the spec.
Simon
| -Original Message-
| From: Ross Paterson [mailto:[EMAIL PROTECTED]]
| Sent: 06 January 2003 12:01
| To:
> > it only happens when i try to compile with profiling enabled.
>
> Profiling (-prof) is incompatible with the native code generator
> (-fasm). Leave out -fasm if you want profiling. (Compiling will be
> slower without -fasm)
>
> It is only a tiny bug: GHC should complain about incompatible o
> After a day of running gdb in parallel on my MacOS X and Linux [quite
> annoying because of different keyboard layouts ;-) ], I've
> come to the following conclusion:
>
> The entry code for BCOs expects all parameters to be on the
> stack, but
> on non-x86 machines, the stg_ap_*_ret pass pa
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
