Behaviour of readProcess, and code simplicity (or lack thereof)

2013-11-15 Thread Duncan Coutts
Hi possibly-interested souls, In this patch to System.Process.readProcess from last year: https://ghc.haskell.org/trac/ghc/changeset/b5ee908863882d18e4110d96b43ccc1bb5068ceb/process Bas changed things so that if an async exception is received by the thread calling readProcess (or readProcessWith

Re: Behaviour of readProcess, and code simplicity (or lack thereof)

2013-11-20 Thread Yitzchak Gale
Whether or not we provide Duncan's proposed interface, we need to add prominent warnings about this to the documentation for every function that has this issue. People need to be aware that the result of an async exception will be a gunshot to the head. On Fri, Nov 15, 2013 at 11:59 PM, Duncan Co

Re: Behaviour of readProcess, and code simplicity (or lack thereof)

2013-11-21 Thread Akio Takano
Hi, On Sat, Nov 16, 2013 at 6:59 AM, Duncan Coutts wrote: > Hi possibly-interested souls, > > In this patch to System.Process.readProcess from last year: > > > https://ghc.haskell.org/trac/ghc/changeset/b5ee908863882d18e4110d96b43ccc1bb5068ceb/process > > Bas changed things so that if an async