Michael Hobbs wrote: > Here's my stab at it. (NB: This is simply an off-the-cuff attempt. It > looks like it should work right, but it is far from rigorously tested or > analyzed.) <grumble/> I discovered a path that would cause a deadlock in that code as well. However, I have a change that /should/ prevent the deadlock. If anyone's interested, email me privately, so I don't waste this list's bandwidth with continuous revisions. - Michael Hobbs
- Trivial Haskell Concurrency problem George Russell
- Re: Trivial Haskell Concurrency problem Michael Hobbs
- Trivial Haskell Concurrency problem Tom Pledger
- Trivial Haskell Concurrency problem Tom Pledger
- Re: Trivial Haskell Concurrency problem Michael Hobbs
- Re: Trivial Haskell Concurrency problem Michael Hobbs
- Re: Trivial Haskell Concurrency problem Michael Hobbs
- Re: Trivial Haskell Concurrency pro... George Russell
- RE: Trivial Haskell Concurrency problem Simon Peyton-Jones
- Re: Trivial Haskell Concurrency problem George Russell
- Re: Trivial Haskell Concurrency problem Wolfram Kahl
- Re: Trivial Haskell Concurrency problem Marcin 'Qrczak' Kowalczyk
- Re: Trivial Haskell Concurrency problem George Russell
- RE: Trivial Haskell Concurrency problem Simon Peyton-Jones
- Re: Trivial Haskell Concurrency problem Wolfram Kahl
- Re: Trivial Haskell Concurrency problem George Russell
- Re: Trivial Haskell Concurrency problem George Russell