[Boost-users] Unlock / free a boost::asio::strand in beast?

Hi, The application is using beast / websockets to communicate with a websocket server. A specific onread handler which is initially running on the stream strand needs to read another value from the websocket server to proceed. It sends a message and then waits on a future. This deadlocks the

[Boost-users] [release] Boost 1.79.0

Release 1.79.0 of the Boost C++ Libraries is now available. These open-source libraries work well with the C++ Standard Library, and are usable across a broad spectrum of applications. The Boost license encourages both commercial and non-commercial use. This release contains numerous enhancemen

Re: [Boost-users] [release] Boost 1.79.0

On Wed, Apr 13, 2022 at 8:13 AM Marshall Clow via Boost-users wrote: > Release 1.79.0 of the Boost C++ Libraries is now available. Thanks! ___ Boost-users mailing list Boost-users@lists.boost.org https://lists.boost.org/mailman/listinfo.cgi/boost-users

[Boost-users] [Math / Special Functions] Use more than one user_error function?

I am wrapping some boost special functions as NumPy "ufuncs" for the Python library SciPy, and I am setting a policy to control how errors are handled. For example, the wrapper of erf_inv (for C++ types float, double and long double) is wrapped as the function scipy.special.erfinv (i.e. the Python

Re: [Boost-users] [release] Boost 1.79.0

On Wed, Apr 13, 2022 at 8:13 AM Marshall Clow via Boost-users wrote: > Release 1.79.0 of the Boost C++ Libraries is now available. The thing that I absolutely LOVE about a new release of Boost, is that someone always reports a crashing bug just after the release is published:

Re: [Boost-users] [Math / Special Functions] Use more than one user_error function?

On 13/04/2022 17:15, Warren Weckesser via Boost-users wrote: I am wrapping some boost special functions as NumPy "ufuncs" for the Python library SciPy, and I am setting a policy to control how errors are handled. For example, the wrapper of erf_inv (for C++ types float, double and long double) i

Re: [Boost-users] [release] Boost 1.79.0

On 13/04/2022 19:04, Vinnie Falco via Boost-users wrote: The thing that I absolutely LOVE about a new release of Boost, is that someone always reports a crashing bug just after the release is published: That's the beauty of modern technology espec

Re: [Boost-users] Unlock / free a boost::asio::strand in beast?

On 13/04/2022 20:15, Markus Bonk wrote: A specific onread handler which is initially running on the stream strand needs to read another value from the websocket server to proceed. It sends a message and then waits on a future. This deadlocks the websocket communication. Don't block in asio h

Re: [Boost-users] [boost] [release] Boost 1.79.0

On Wed, Apr 13, 2022 at 3:17 PM Andrey Semashev wrote: > > On 4/13/22 21:04, Vinnie Falco via Boost wrote: > > The thing that I absolutely LOVE about a new release of Boost, is that > > someone always reports a crashing bug just after the release is > > published: > > > >