Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Concurrency seems to mean Parallelism #130

Open
jpetso opened this issue Aug 6, 2015 · 0 comments
Open

Concurrency seems to mean Parallelism #130

jpetso opened this issue Aug 6, 2015 · 0 comments

Comments

@jpetso
Copy link
Contributor

jpetso commented Aug 6, 2015

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?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants