You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
All the libraries in the Concurrency category specialize in programming for parallel computation. When I read "Concurrency" (especially with subtitle "Concurrency and Multithreading"), I would expect Boost.Asio, Boost.Future, CAF (C++ Actor Framework) etc., maybe a link to C++11 threads.
The Committee seems to agree and names their working groups "Concurrency" for standardizing Boost.Future, mutex stuff and Asio's executors, and "Parallelism" for parallel algorithms, SIMD and whatnot.
I suggest to have "Concurrency" renamed to "Parallelism". Not sure what to do about the items that would go into an actual "Concurrency" section, since Boost.Future is most certainly not an Asynchronous Event Loop but as one of the most generically useful and close-to-being-standardized libraries should definitely have a place in this list. On the other hand, libuv isn't so much concerned with concurrency and really more with batching of asynchronous stuff under the hood. So maybe just have two separate categories with some of the same items in both?
The text was updated successfully, but these errors were encountered:
All the libraries in the Concurrency category specialize in programming for parallel computation. When I read "Concurrency" (especially with subtitle "Concurrency and Multithreading"), I would expect Boost.Asio, Boost.Future, CAF (C++ Actor Framework) etc., maybe a link to C++11 threads.
The Committee seems to agree and names their working groups "Concurrency" for standardizing Boost.Future, mutex stuff and Asio's executors, and "Parallelism" for parallel algorithms, SIMD and whatnot.
I suggest to have "Concurrency" renamed to "Parallelism". Not sure what to do about the items that would go into an actual "Concurrency" section, since Boost.Future is most certainly not an Asynchronous Event Loop but as one of the most generically useful and close-to-being-standardized libraries should definitely have a place in this list. On the other hand, libuv isn't so much concerned with concurrency and really more with batching of asynchronous stuff under the hood. So maybe just have two separate categories with some of the same items in both?
The text was updated successfully, but these errors were encountered: