rsevents VS libpthread

Thanks. Perhaps I did go overboard with that disclaimer.. probably because I myself made the mistake of initially using [0] the oh-so-convenient tokio::io::copy() instead of writing my own copy method that would drop the other half of the connection when one side was closed.

The copy_with_abort() routine is still taking the easy way out in this not-optimized-for-heavy-production-use sample because it uses a broadcast channel per connection to reactively signal that the other half of the connection should be closed (rather than timing out every x ms to see if an abort flag has been set). In the real world, I'd probably replace the join! macro with a manual event loop to be able to do the same but without creating a broadcast channel per-connection.

(I maintain an extremely lightweight "awaitable bools" library for rust [1] that is perfect for this kind of thing (roughly equivalent to a "bounded broadcast_channel<()> of queue length 1, but each "channel" is only a single (optionally stack-allocated) byte) — but it's for event loops in synchronous code and not async executor compatible.)

[0]: https://github.com/mqudsi/tcpproxy/commit/0164ef836a49f2f738...

[1]: https://github.com/neosmart/rsevents

The AutoResetEvent takes care of that, doing Acquire and Release as needed. Source code here if you’re interested, not too long: https://github.com/neosmart/rsevents/blob/master/src/lib.rs

I wrote my own FOSS signals/events library in C++ [0] and in rust [1] (atop of parking lot as a futex shoe-in) and I disagree. This has nothing to do with the language and everything to do with the semantics of the locks. Writing concurrency primitives is HARD and the more functionality your API exposes, the more room there is for nuanced bugs in how everything interplays with everything else.

[0]: https://github.com/neosmart/pevents

[1]: https://github.com/neosmart/rsevents

rsevents-extra types are built on top of the low-level synchronization types from the rsevents crate, which are fast and tiny (one-byte) Send + Sync synchronization types for signalling one or more waiting threads (à la WIN32 events), doing everything but putting a thread to sleep in userland.

For example, macOS is a POSIX-certified system. The implementation for Pthread is lib_pthread. The macOS SDK, which developers can download for free, provides the header file pthread.h and clang, the compiler and linker. I'd recommend downloading Xcode, which has the SDK included.

macOS uses its own pthreads implementation: https://github.com/apple-oss-distributions/libpthread