In case anyone was wondering what this state-threads thing I keep
talking about is, here is a sample implementation (in C) as well as a
lot of documentation and FAQs that apply to haskell as well.
http://state-threads.sourceforge.net/
it should be noted that the chief disadvantage of state
On 31 March 2006 13:41, John Meacham wrote:
I have tried to summarize the current thinking into a proposal on the
wiki.
http://haskell.galois.com/cgi-bin/haskell-prime/trac.cgi/wiki/Concurrenc
y
I split it into 3 parts.
the standard - all haskell' compilers must implement
optional
On Sat, Apr 01, 2006 at 02:30:30PM +0400, Bulat Ziganshin wrote:
new stacks can be allocated by alloca() calls. all these
alloca-allocated stack segments can be used as pool of stacks assigned
to the forked threads. although i don't tried this, my own library
also used processor-specific
On Fri, Mar 31, 2006 at 01:15:03PM -0800, John Meacham wrote:
On Fri, Mar 31, 2006 at 04:21:26PM +0100, Simon Marlow wrote:
Great. Apart from my misgivings about allowing cooperative scheduling
at all, here's a few comments on the proposal:
much much preferable to a standard that not
Hello John,
Monday, April 3, 2006, 12:53:05 PM, you wrote:
new stacks can be allocated by alloca() calls. all these
alloca-allocated stack segments can be used as pool of stacks assigned
to the forked threads. although i don't tried this, my own library
also used processor-specific method.
GHC 6.4 has rather conservative constraints on instances to guarantee
termination. GHC 6.5 has more liberal constraints; see
http://haskell.galois.com/cgi-bin/haskell-prime/trac.cgi/wiki/FlexibleInstances
Unfortunately instances generated by newtype-deriving need not satisfy
either of these
On Mon, Apr 03, 2006 at 11:38:08AM +0100, Ross Paterson wrote:
On Fri, Mar 31, 2006 at 01:15:03PM -0800, John Meacham wrote:
On Fri, Mar 31, 2006 at 04:21:26PM +0100, Simon Marlow wrote:
Great. Apart from my misgivings about allowing cooperative scheduling
at all, here's a few comments
John Meacham wrote (... but I've reordered things):
My only real 'must-have' is that the 4 modes all can be explicitly and
unambiguously specified. I have opinions on the syntax/hints but
that is
more flexable.
I basically agree (the syntax discussion will take place in the years
after
