Leonard Hecker

I wrote down my thoughts about this here: https://github.com/rust-lang/rfcs/pull/2033#issuecomment-309212006 tl;dr: I see the future of coio etc. a bit pessimistic and fully expect a mediocre solution consisting out of async/await...

@zonyitoo Yup that's basically why we asked the Rust devs to reconsider and stop using TLS for panics in the stdlib back then when we worked on coio. Since they...

I think we might have to check for the `unwind` flag [here](https://github.com/glasswings/coio-rs/blob/issue-51/src/coroutine.rs#L62) too and in that case directly proceed to [here](https://github.com/glasswings/coio-rs/blob/issue-51/src/coroutine.rs#L81). Is that correct, @zonyitoo?

@glasswings it does not work because you'd need to check for `data == X` where `X` must be some invalid address except for `0`. The reason for this is that...

@glasswings How's it going? Should one of us take a look? We could continue development of this as well if something is left. And if you want to: My offer...

We really should keep this issue open until we've found the reason. It's not that bad that this method can't be inlined safely but it still annoys me to no...

Hey @glasswings! If you intend to stick with this project for a while I can offer you to give you a quick introduction into how coio works and answer all...

Hi! I'm not quite sure what you'd like to achieve... Are you trying to artificially limit the number of open TCP connections to a safe value (by forcibly closing old...

If you use `shutdown(socket_fd, SHUT_RDWR);` you can let blocking `read()`/`write()` calls return with a 0 return value. The remaining problem here is that this won't wake up the event loop,...

I don't think your 3 solutions will work, because if a coroutine is still stuck in I/O it will _never_ anymore be woken up after you called `close()` or `shutdown()`...