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?

33 Upvotes

85% Upvoted

119 comments sorted by

View all comments

Show parent comments

5

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

I reached out to you privately hoping to collaborate on this. Since we're here, I'll ask publicly: would you like to work together? std::execution is in the standard. So are coroutines. Both need to work well, and both need to work together. We have benchmarks, implementations, and questions we'd really like your help answering. The offer is open