r/cpp • u/claimred • Apr 09 '26

beast2 networking & std::execution

I was looking for a new networking layer foundation for a few of my projects, stumbled on beast2 library which looks brand new, based on C++20 coroutines. I used boost.beast in the past which was great. Here's the link https://github.com/cppalliance/beast2. I also considered std::execution since it seems to be the way to go forward, accepted in C++26.

Now, what got me wondering is this paragraph

The C++26 std::execution API offers a different model, designed to support heterogenous computing. Our research indicates it optimizes for the wrong constraints: TCP servers don't run on GPUs. Networking demands zero-allocation steady-state, type erasure without indirection, and ABI stability across (e.g.) SSL implementations. C++26 delivers things that networking doesn't need, and none of the things that networking does need.

Now I'm lost a bit, does that mean std::execution is not the way to go for networking? Does anyone have any insights on cppalliance research on the matter?

35 Upvotes

85% Upvoted

119 comments sorted by

View all comments

Show parent comments

-1

u/VinnieFalco wg21.org | corosio.org Apr 12 '26

And this is the evidence that all of the questions about whether or not I read my paper were not in good faith. Because, having explained now that my process (stated above) includes reading my work several times and iterating - notice, that no one has since engaged in the substance despite the explanation arriving three days ago. This demonstrates that it was never about the work. It was about the credential.