FoundationDB's Flow – Bringing Actor-Based Concurrency to C++11
1–10 of 38 posts
Re: FoundationDB's Flow – Bringing Actor-Based Concurrency to C++11
#2A previous discussion: https://news.ycombinator.com/item?id=46191763
Re: FoundationDB's Flow – Bringing Actor-Based Concurrency to C++11
#3This looks kind of outdated, especially since we are on C++23 as latest approved standard, and co-routines would be a better approach since C++20.
Also how is the supposed Swift rewrite going on?
Re: FoundationDB's Flow – Bringing Actor-Based Concurrency to C++11
#4A previous discussion: https://news.ycombinator.com/item?id=46191763
Thanks! Macroexpanded:
Flow: Actor-based language for C++, used by FoundationDB - https://news.ycombinator.com/item?id=46191763 - Dec 2025 (53 comments)
Re: FoundationDB's Flow – Bringing Actor-Based Concurrency to C++11
#5This looks kind of outdated, especially since we are on C++23 as latest approved standard, and co-routines would be a better approach since C++20. Also how is the supposed Swift rewrite going on?
Just because coroutines exist doesn’t mean everything should use them for concurrency.
Why would it be better? It’s pretty easy to set up threads in general.
Re: FoundationDB's Flow – Bringing Actor-Based Concurrency to C++11
#6This looks kind of outdated, especially since we are on C++23 as latest approved standard, and co-routines would be a better approach since C++20. Also how is the supposed Swift rewrite going on?
You're in luck: https://github.com/apple/foundationdb/blob/main/design/corou...
Re: FoundationDB's Flow – Bringing Actor-Based Concurrency to C++11
#7This looks kind of outdated, especially since we are on C++23 as latest approved standard, and co-routines would be a better approach since C++20. Also how is the supposed Swift rewrite going on?
Just because coroutines exist doesn’t mean everything should use them for concurrency. Why would it be better? It’s pretty easy to set up threads in general.
Threads use more system resources than coroutines so it can be a big deal when you can potentially have thousands of them running.
Re: FoundationDB's Flow – Bringing Actor-Based Concurrency to C++11
#8Re: FoundationDB's Flow – Bringing Actor-Based Concurrency to C++11
#9This looks kind of outdated, especially since we are on C++23 as latest approved standard, and co-routines would be a better approach since C++20. Also how is the supposed Swift rewrite going on?
Just because coroutines exist doesn’t mean everything should use them for concurrency. Why would it be better? It’s pretty easy to set up threads in general.
The management to handle Threading and IO and not get it wrong is pretty high unless you’re using something like Rust because it guarantees you’re safe, vs letting the routine runtime management handle everything for you for free
Re: FoundationDB's Flow – Bringing Actor-Based Concurrency to C++11
#10This looks kind of outdated, especially since we are on C++23 as latest approved standard, and co-routines would be a better approach since C++20. Also how is the supposed Swift rewrite going on?
[flagged]