News for hackers. Stuff that matters.
Re:Why asynchronous Rust doesn't work by pumpkinpal on Wednesday March 10, 2021 @05:32PM (#26417338)
Would anyone be able to make some brief comparisons between Rust's asynchronous model and the model followed by Asio in C++ (on which C++23 executors/networking is based) and if there are any parallels with the sender/receiver concept (https://www.youtube.com/watch?v=h-ExnuD6jms)?

I've seen a few comments talking about the choice of Rust adopting a poll model as opposed to a completion model. Am I correct in assuming these are the same things as a reactor (kqeue/epoll etc.) vs a proactor (IOCP) and that a proactor can be implemented in terms of a reactor.

Re:Why asynchronous Rust doesn't work by steveklabnik on Wednesday March 10, 2021 @05:49PM (#26417492)
I don't know enough about Asio to make a good comparison, but

> Am I correct in assuming these are the same things as a reactor (kqeue/epoll etc.) vs a proactor (IOCP)

Close enough, yes.

> a proactor can be implemented in terms of a reactor.

Yes.