On Mon, Nov 29, 2010 at 9:49 PM, wren ng thornton wrote:
> Isn't that pretty normal?
>>
>
> The blocking for someone to open the other end is perfectly normal. The
> fact that compiling with -threaded takes a perfectly working program and
> makes it consistently crash I wouldn't call "normal".
>
On 11/29/10 6:36 PM, Bryan O'Sullivan wrote:
On Sat, Nov 27, 2010 at 9:05 PM, wren ng thornton wrote:
So I've just started playing around with STM and -threaded programs and
I've run into a bug. The bug is similar to [1] except that the file in
question is a Posix FIFO instead of a Bluetooth d
On Sat, Nov 27, 2010 at 9:05 PM, wren ng thornton wrote:
> So I've just started playing around with STM and -threaded programs and
> I've run into a bug. The bug is similar to [1] except that the file in
> question is a Posix FIFO instead of a Bluetooth device. Same behavior:
> always errors with
On Mon, Nov 29, 2010 at 01:29:10PM +1100, Manuel M T Chakravarty wrote:
> Ian Lynagh:
> > On Sun, Nov 28, 2010 at 12:56:00PM -0800, Mark Lentczner wrote:
> >>
> >> Outstanding question is what should this framework be called? I would like
> >> to continue to call it GHC.framework, but change the
On 25/11/2010 20:01, Roman Leshchinskiy wrote:
On 25/11/2010, at 10:33, José Pedro Magalhães wrote:
Is this a bug, or is the value of spec-constr-count being
manipulated in some way for certain passes?
spec-constr-count decreases for nested specialisations. For instance,
if spec-constr-count
On 26/11/2010 10:00, Jean-Marie Gaillourdet wrote:
Hi all,
I've been searching information regarding file handles to pipes created by
System.Process.createProcess. The documentation does not state whether they are
in binary mode, i.e. whether they have line ending conversion or an encoding
en
On 29/11/2010 02:05, Wolfram Kahl wrote:
Hello,
with a large Agda development, I have a reproducible segmentation fault
that I have been able to localise to the serialisation
(Agda.TypeChecking.Serialise.encode), which heavily relies on Data.HashTable.
Now I find that Data.HashTable (from GH
I think it would help to separate issues.
If it were not for rebindable syntax, there would be no need for these "op"
fields in (say) BindStmt etc. Instead, we'd have a fixed typing rule for
BindStmt, and the desugarer would use the fixed Control.Monad.(>>=). The
rebindable syntax thing just