Fergus Henderson wrote:
I think the issue here is that in ghc (with -fglasgow-exts),
the a here refers to the same type variable a in the
top of the instance declaration, which has already been
constained, and cannot be constrained again.
Is that a bug or a feature?
With Haskell 98, it is a fresh
Christian Maeder [EMAIL PROTECTED] writes:
Fergus Henderson wrote:
I think the issue here is that in ghc (with -fglasgow-exts),
the a here refers to the same type variable a in the
top of the instance declaration, which has already been
constained, and cannot be constrained again.
Is
Hi,
I have a question which came up as a result of some attempts to enforce
seperate compilation. Suppose we have two modules as follows:
-- A.hs
module A (AbstractType) where
data AbstractType = it's hidden implementation
f :: AbstractType - String
f _ = foo
g :: AbstractType
g =
ok, I guess this is not something you do every day;
I am making a language binding for the library Allegro which has some
weird things going on. I need to make a main() in C.
so I followed the manual, I export my non-main haskell entrypoint
and call it from the C main which basically is
the runtime for a set of 100 tests with different inputs where:
1. 751 ms
2. 932 ms (factor 1.24)
3. 3074 ms (factor 4.09)
I think we ought to be able to get that down further. Could you post
the code again? It probably should go in our benchmark suite too.
Cheers,
Simon
ok, I guess this is not something you do every day;
I am making a language binding for the library Allegro which has some
weird things going on. I need to make a main() in C.
so I followed the manual, I export my non-main haskell entrypoint
and call it from the C main which basically is
On Mon, 8 Dec 2003, Simon Marlow wrote:
Date: Mon, 8 Dec 2003 12:20:42 -
From: Simon Marlow [EMAIL PROTECTED]
To: [EMAIL PROTECTED], [EMAIL PROTECTED]
Subject: RE: replacement of main
ok, I guess this is not something you do every day;
I am making a language binding for the library
