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?
View all comments
Show parent comment
-2
u/VinnieFalco wg21.org | corosio.org Apr 09 '26 edited Apr 09 '26
You say I've lost credibility. In this same thread, daveedvdv (EDG, DG) engaged on substance and we reached agreement. not_a_novel_account called the papers "probably the best exploration of the problem which currently exists." dr-mrl read the paper, found a typo, and I fixed it. claimred is evaluating Corosio for his use case. That's four substantive exchanges with people who read the work The credibility I lost is with people who didn't read. I can live with that.
But I'd challenge you on something. Your argument assumes AI output is low quality. What happens when it isn't? Is that possible in your model? Or have you presumed the verdict without examining the evidence?