Ximin Luo

>> Please use return instead of pure > > Sorry, I will do this, this is just an automatic habit for me. My understanding is that newer Haskell code prefers...

> Please use HostName instead of String Done in 1c11e49, it requires moving the aliases from Info into Types. Since PortNumber is already in Types, I think the new location...

> @infinity0 What is your endpoint based on? RFC3986? The concept fits parts of the ideas in that RFC, but it originates more directly from my years of experience programming...

This won't be able to enter Debian until Google's C++ webrtc library can be built as a public shared library ("component_build=on" in their terminology). We cannot distribute binary blobs like...

Generally when you notice a pattern, you should think harder before calling it a coincidence. :) A blocking queue of capacity 0 that works as I described is a well-known...

Why would you consider other people claiming the current behavior is "incorrect" as a "recipe for bad discussion"? Generally, bugs exist, and people have different opinions on things including what...

No, capacity 1 doesn't work - the difference is as I described in my first post. There is a cross-language common convention for the behaviour here.

The general motivation is to ensure the message passing happens atomically / synchronously and there is no "gap" in the middle which forces you to think about distributed systems topics....

Sorry; I wrote the original code in #14 and was less familiar with strictness then, I assumed it was fine as it passed review. FWIW, I did intend the strict...

> On an unrelated note, perhaps the elements of the tuple should be swapped to mirror atomicModifyIORef? The intention was to mirror `state` as in `MonadState`, `StateT`, etc. I speculate...