MIO VS rust-zmq

Was playing around with mio (https://github.com/tokio-rs/mio) (not that mio itself is very important here!) and was trying to implement a simple something that I've done in java before: a Reactor that you can register ReactorClients with that will get callback whenever there are events on the corresponding socket etc.

How does it compare to mio?

TcpStream gets its wake behavior by delegating to the fd wakers. The Unix wakers have a few implementations, for different platforms. On Linux and Android, epoll is used.

The real implementation details of the I/O event queue is done in mio as u/hniksic pointed out, but that's more comparable with libuv which is certainly a huge part of the Node runtime. mio and libuv have a lot of similarities (at least they used to).

My example was "twice by one developer", not "twice across all indexed repos."

A spot check shows that quite a few in your link are used specifically to ensure correct handling of Rust multi-level breaks work syntax, like https://github.com/rust-lang/rust-analyzer/blob/master/crate... , https://github.com/rust-lang/rustfmt/blob/master/tests/sourc... , https://github.com/rust-lang/rust/blob/master/src/tools/rust... , https://github.com/rust-lang/rust/blob/master/src/tools/rust... and likely more.

Another is a translation of BASIC code to Rust, using break as a form of goto. https://github.com/coding-horror/basic-computer-games/blob/e...

The example at https://github.com/tokio-rs/mio/blob/master/tests/tcp.rs is a nice one

    // Wait for our TCP stream to connect

In my program, I have about 6 different components that follow the pattern below. Basically, the components run a thread while polling on crossbeam channels, file descriptors or sockets. For polling, I am using Mio (https://github.com/tokio-rs/mio).

On the code side it's pretty much the same as C++. You have a module that defines an interface and per-platform implementations that are included depending on a "configuration conditional checks" #[cfg(target_os = "linux")] macro.

https://github.com/tokio-rs/mio/blob/c6b5f13adf67483d927b176...

Made possible by Wasi support for Mio https://github.com/tokio-rs/mio/pull/1576

Indeed! In practice it's done through the polling operation: instead of a separate poll for op1 and op2, the program essentially tells the OS "wake me when either op1 or op2 is ready" (through the epoll syscall on Linux). The mio crate implements this, and the example on the readme is basically the same loop, but written with this polling strategy in mind.

It depends how useful you think the patch is, and maybe also how likely you think it will get merged.

In most cases I simply keep my fork as a PR and use the package either by vendoring or directly from the repo. If anyone else encounters the same bug, they will see my PR referencing the issue, they can do the same.

If many people are encountering the bug and using the package, and/or if the project seems dead, then it's a good idea to publish. You can do username prefix or you can just add "2" at the end. I've seen this for other repos, This is what https://crates.io/crates/zmq2 did while https://crates.io/crates/zmq was inactive, though it seems like the latter's maintainer became active and merged what the former's maintainer had done.

I have been using https://crates.io/crates/zmq since 2015 (shortly after rust 1.0 was announced) in production with pub-sub, request-reply and router without any issue. Processes about 5k msg/seconds (mid-freq market data).

I learned a lot about sockets with the library ZeroMQ, although at that time I was using the Python version. This library also has a Rust library, although it doesn't look like the amazing guide about sockets allows you to select Rust as of yet. Still I would recommend going through this guide, as it is not just teaching you how to use a library, but also teaches you about sockets at a theoretical level. It's entertaining to read as well.

I think maybe the ZeroMQ rust crate as a case study is something that is non-trivial: https://github.com/erickt/rust-zmq