-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 9/7/10 05:08 , David Virebayre wrote:
> 2010/9/7 Ben Lippmeier :
>> Though be warned you must use a recent GHC head build to get good
>> performance. After GHC 7.0 is out (in a few weeks) we'll be able to release
>> a properly stable version.
>
>
> This is not stupid, but yes you missed something :)
> http://www.reddit.com/r/haskell/comments/dad6j/unless_theres_a_major_hiccup_itll_be_in_ghc_70/
Oh, I saw that thread, but at the time it had vrey few comments, so I
definately missed something !
Thanks !
David.
_
2010/9/7 David Virebayre :
> 2010/9/7 Ben Lippmeier :
>> Though be warned you must use a recent GHC head build to get good
>> performance. After GHC 7.0 is out (in a few weeks) we'll be able to release
>> a properly stable version.
>
> Pardon a probably stupid question, but did I miss something ?
2010/9/7 Ben Lippmeier :
> Though be warned you must use a recent GHC head build to get good
> performance. After GHC 7.0 is out (in a few weeks) we'll be able to release a
> properly stable version.
Pardon a probably stupid question, but did I miss something ?
http://hackage.haskell.org/trac/g
On 07/09/2010, at 6:11 PM, Johannes Waldmann wrote:
> Mathew de Detrich gmail.com> writes:
>
>> Haskell is still by far one of the best languages
>> to deal with concurrency/parallelism.
>
> Sure, I fully agree.
>
> I am using concurrency (with explicit forkIO, communication via Chan)
> a
Mathew de Detrich gmail.com> writes:
> Haskell is still by far one of the best languages
> to deal with concurrency/parallelism.
Sure, I fully agree.
I am using concurrency (with explicit forkIO, communication via Chan)
a lot (my Haskell application controls several external constraint solve
*Mistake, in where I said "majority of Haskell programs were pure" I meant
"majority of code in Haskell programs was pure"
On Tue, Sep 7, 2010 at 11:07 AM, Mathew de Detrich wrote:
> Before Haskell took off with parallelism, it was assumed that Haskell would
> be trivial to run concurrently on co
Before Haskell took off with parallelism, it was assumed that Haskell would
be trivial to run concurrently on cores because majority of Haskell programs
were pure, so you could simply run different functions on different cores
and string the results together when your done
It turned out that using
waldmann:
> > > functional/declarative code "automatically" parallelizes,
>
> > Well, that's not really a good thing to say.
>
> Sure, sure, and I expand on the details in my lectures.
>
> But in advertising (the elevator sales pitch), we simplify.
> Cf. "well-typed programs don't go wrong".
>
> > functional/declarative code "automatically" parallelizes,
> Well, that's not really a good thing to say.
Sure, sure, and I expand on the details in my lectures.
But in advertising (the elevator sales pitch), we simplify.
Cf. "well-typed programs don't go wrong".
- Johannes.
__
waldmann:
> Don Stewart galois.com> writes:
>
> > Note that DPH is a programming model, but the implementation currently
> > targets shared memory multicores (and to some extent GPUs), not
> > distributed systems.
>
> Yes. I understand that's only part of what the original poster wanted,
> but I
Don Stewart galois.com> writes:
> Note that DPH is a programming model, but the implementation currently
> targets shared memory multicores (and to some extent GPUs), not
> distributed systems.
Yes. I understand that's only part of what the original poster wanted,
but I'd sure want to use ghc-ge
waldmann:
> http://book.realworldhaskell.org/read/concurrent-and-multicore-programming.html
>
> http://www.haskell.org/haskellwiki/GHC/Data_Parallel_Haskell
> Although the last two edits on that page are from 2010 and 2009.
> So what *is* the current status of DPH?
>
Note that DPH is a programmi
http://book.realworldhaskell.org/read/concurrent-and-multicore-programming.html
http://www.haskell.org/haskellwiki/GHC/Data_Parallel_Haskell
Although the last two edits on that page are from 2010 and 2009.
So what *is* the current status of DPH?
J.W.
_
14 matches
Mail list logo
