Mathieu Boespflug
Mathieu Boespflug
> There are discussions underway about the naming of withMonitorRef or deprecating the old API (which I agree with) For reference, in #281.
Erlang does not flush by default, but as @hyperthunk says, gives you the option to. Makes sense to copy Erlang, with an `unmonitorFlush` variant or somesuch.
Well, except that Erlang only kept the non-flush variant by default due to backwards compatibility... http://erlang.org/pipermail/erlang-questions/2008-August/037564.html
It's true that there's a potential performance concern here. But i don't think we should choose the semantics based on the details of how things are implemented today. If one...
I'm not sure what exactly the problem is here. Until `unlink` completes, because I called `link`, I accept that I'll have some exception thrown at me at any time. So...
There is no need to bracketize `unlink` because if `unlink` doesn't get called that's quite okay: `link` is just there to signal that the current thread should have an async...
> These tests break connections with testBreakConnection, which doesn't deliver EventConnectionLost > isn't this a bug specific to the network-transport backend being used during tests?
Then move issue to e.g. n-t-tcp? Does n-t-inmemory suffer from the same problem?
`{}`, `()` and `[]` are all symbols that come in pairs, but in Haskell that's where the similarity stops. Unlike `(...)` and `[...]`, `{...}` is never an expression. In fact,...
Example 1 will stay on a single line if the input is on a single line. If you want multiple lines but also multiple list items on each line, break...