Aha. That's a bug. The forall'd type variables of an expression type
signature should scope over the expression.
Thank you -- I'll fix it, though I don't know if it'll get into 6.6 now.
Simon
| -Original Message-
| From: Mirko Rahn [mailto:[EMAIL PROTECTED]
| Sent: 02 October 2006
I'm also willing to try to help investigate/fix problems with GHC on
OS X/i386.
/Björn
On 2 okt 2006, at 09.31, Simon Peyton-Jones wrote:
Thanks -- in fact we've had a few helpful offers of access (which is v
helpful). We may still yet take you up, but meanwhile don't do too
much
work.
Hello John,
(i'm moving thread to the ghc-users where this discussion continues in
ghc-related aspects)
Thursday, September 28, 2006, 3:30:09 AM, you wrote:
So, just to confirm in my mind what you are proposing:
Compiler/Version specific Core:
Yhc.Core, Hugs.Core, GHC.Core
With a
Hello glasgow-haskell-users,
i've uploaded my first attempt to define Core package as
http://www.haskell.org/bz/core20061003.tar.gz
you should use -fno-implicit-prelude to compile it with GHC.
it also compiles with Hugs, although zeroInt and other constant
definitions are definitely wrong :)
Hi Bulat,
i've uploaded my first attempt to define Core package as
http://www.haskell.org/bz/core20061003.tar.gz
Cool. The one thing that worries my slightly is that HugsCore.Bool
imports Prelude, and surely Prelude will end up importing
HugsCore.Bool at some point? It seems that Core needs
Hello Neil,
Tuesday, October 3, 2006, 6:26:42 PM, you wrote:
i've uploaded my first attempt to define Core package as
http://www.haskell.org/bz/core20061003.tar.gz
Cool. The one thing that worries my slightly is that HugsCore.Bool
imports Prelude, and surely Prelude will end up importing
On Tue, Oct 03, 2006 at 06:06:02PM +0400, Bulat Ziganshin wrote:
(i'm moving thread to the ghc-users where this discussion continues in
ghc-related aspects)
I don't see how compiler-independence is a GHC-specific topic.
___
Glasgow-haskell-users
Hello Ross,
Tuesday, October 3, 2006, 10:33:46 PM, you wrote:
On Tue, Oct 03, 2006 at 06:06:02PM +0400, Bulat Ziganshin wrote:
(i'm moving thread to the ghc-users where this discussion continues in
ghc-related aspects)
I don't see how compiler-independence is a GHC-specific topic.
i mean
When I tried to build VSHaskell with the RC2 version of GHC I got the
following error:
src\lib\Registry.hsc:30:0:
Bad interface file: C:\Program Files\Haskell\comlib-0.1\ghc-6.5.20061001/Com
Dll.hi
Something is amiss; requested module comlib-0.1:ComDll differs from nam
e found in the
If I understand the way things work, GHC decides whether or not to emit
the -fno-unit-at-a-time flag in -fvia-C compilation based on whether or
not the gcc used when compiling GHC supported the flag or not. I'm
running into trouble using precompiled GHC snapshots (that were compiled
on
10 matches
Mail list logo