Benoit Vey

I forgot to mention a change about `try-then` in the RFC aiming at handling @sylvanc's concern about nested exceptions. I've updated the RFC.

This was discussed on the sync call yesterday. Several ideas came up, namely using exceptions as a local return. I'll experiment with that and report back.

After taking a look at the signal implementation (`asio/epoll.c` and `asio/kqueue.c`), the behaviour you describe seems to correspond to the OSX implementation. This implementation is, as you point out, not...

@SeanTAllen It could be handled by the runtime. For example by storing a list of ASIO events for each signal, instead of just one.

The main argument I have for treating this as a bug is that the Linux and OSX implementations currently do opposite things.

@sargun Sorry, I forgot to reply to you here. I was incorrect, the OSX implementation is indeed thread safe. The other problems are still relevant, though.

Hm no, the unreachable solution doesn't seem correct. I'll investigate more.

Since an equivalent code without generic types results in a compilation error, I think this match should either result in a compilation error or be considered non-exhaustive. I'm not sure...

I'm not sure the implementation solution described by @jemc above is correct, since it would forbid matching from a type parameter to the same type parameter (e.g. if the match...