On Tue, Feb 07, 2006 at 09:52:49PM +0100, Tomasz Zielonka wrote:
> ... I was wondering if it would be possible ...
>
> There's also a related idea ...
I've heard that the implementation of optimistic evaluation was rather
complex, which was the main reason not to include it in GHC (yet).
That's w
Cyril Schmidt wrote:
> I need to pass a big 2-dimensional array of doubles from a legacy
> C code to a Haskell module. Of this huge array, the Haskell code will
> actually use only
> a few elements (say, 10 out of 100x20 matrix). Unfortunately, the C code
> does not know
> which data are actually n
I need to pass a big 2-dimensional array of doubles from a legacy
C code to a Haskell module. Of this huge array, the Haskell code will
actually use only
a few elements (say, 10 out of 100x20 matrix). Unfortunately, the C code
does not know
which data are actually needed in the Haskell module.
Hello GHC,
Tuesday, February 07, 2006, 8:03:49 PM, you wrote:
G> someone mentioned to me that this expression:
G>mapM_ action [n..m]
G> isn't being optimised properly, so I thought I'd look into it. Sure
may be, what's me :) i use specially written function as faster
version of this idi
On Tue, Feb 07, 2006 at 09:52:49PM +0100, Tomasz Zielonka wrote:
> There's also a related idea to decrease the priority of garbage
> producing threads (and/or increase for garbage reducing threads). This
> way it would be possible to make the idiomatic Haskell 'wc' (word count)
> implementation spa
On Tue, Feb 07, 2006 at 08:28:51PM +, Frederik Eaton wrote:
> What is the status of Rob Ennals' optimistic evaluation work? I'm told
> that it has been removed from GHC. This is extremely depressing to me.
> Without such a feature available, it becomes very difficult to write
> programs that p
Hi all,
What is the status of Rob Ennals' optimistic evaluation work? I'm told
that it has been removed from GHC. This is extremely depressing to me.
Without such a feature available, it becomes very difficult to write
programs that process large amounts of data in Haskell. In many such
applicati
I agree 100% with you. We absolutely do intend to support 6.4.2 as a
stable compiler for a long time yet. But this particular bug has been
in the compiler for years, and only reported once. I very much doubt
that anyone will even notice whether or not we fix 6.4.2.
Still, if any two people (