I would like them to be in asio, but I am not the asio author. Chris did not seem interested in the idea. On Tue, Mar 7, 2023 at 3:39 PM wrote:

Hi.

I've a simple question: those are primitives built around asio, and according to the documentation you say "This library is not meant as the default method of synchronization of asio-based apps, but to be used by library developers.", so there's a reason to create a different library instead that trying to merge them directly into boost::asio?

Regards

Daniele Lupo

-----Original Message----- From: Boost On Behalf Of Klemens Morgenstern via Boost Sent: Tuesday, March 7, 2023 6:13 AM To: boost@lists.boost.org Cc: Klemens Morgenstern Subject: [boost] boost.asem seeking endorsement

Heya Boost Community,

I am seeking endorsement for my boost.asem library.

It provides the following asio-based synchronization primitives:

- barrier - condition_variable - mutex - semaphore

Asio currently has timers & (experimental) channels that can help. However, I think there is a need for more purpose-made utilities to help more complex asio-based libraries (requests, redis, mysql et al.)

Code: https://github.com/klemens-morgenstern/asem Docs: https://klemens.dev/asem/

I'm also not too happy with the name, but so far I only came up with an acronym: Semaphore, Condition_variable, And Mutex. Suggestions are welcome.

_______________________________________________ Unsubscribe & other changes: http://lists.boost.org/mailman/listinfo.cgi/boost