BS::thread_pool: a fast, lightweight, and easy-to-use C++17 thread pool library
reset() which caused it to create the wrong number of threads.README.md, so I moved it to a separate file, CHANGELOG.md.README.md.promise has been renamed to task_promise to avoid any potential errors in case the user invokes using namespace std.submit() now catches exceptions thrown by the submitted task and forwards them to the future. See this issue.-Weffc++ flag in GCC. See this pull request.parallelize_loop() which prevented it from actually running loops in parallel, see this issue.and as && by default, the previous release did not compile with MSVC unless the /permissive- or /Za compiler flags were used. This has been fixed in this version, and the code now successfully compiles with GCC, Clang, and MSVC. See this pull request.README.md.README.md.get_tasks_queued() gets the number of tasks currently waiting in the queue to be executed by the threads.get_tasks_running() gets the number of tasks currently being executed by the threads.get_tasks_total() gets the total number of unfinished tasks - either still in the queue, or running in a thread.get_tasks_running() == get_tasks_total() - get_tasks_queued().tasks_waiting to tasks_total to make its purpose clearer.paused is set to true, the workers temporarily stop popping new tasks out of the queue, although any tasks already executed will keep running until they are done. Set to false again to resume popping tasks.wait_for_tasks() will wait for the running tasks instead of all tasks (otherwise it would wait forever).reset() can now change the number of threads on-the-fly while there are still tasks waiting in the queue. The new thread pool will resume executing tasks from the queue once it is created.parallelize_loop() and wait_for_tasks() now have the same behavior as the worker function with regards to waiting for tasks to complete. If the relevant tasks are not yet complete, then before checking again, they will sleep for sleep_duration microseconds, unless that variable is set to zero, in which case they will call std::this_thread::yield(). This should improve performance and reduce CPU usage.windows.h.README.md file has been reorganized and expanded.std::move from the return statement in push_task(). This previously generated a -Wpessimizing-move warning in Clang. The assembly code generated by the compiler seems to be the same before and after this change, presumably because the compiler eliminates the std::move automatically, but this change gets rid of the Clang warning.std::cout, which was left in the code by mistake.parallelize_loop() no longer sends references for the variables start and stop when calling push_task(), which may lead to undefined behavior.README.md has been updated, and it is now roughly identical in content to the paper.std::this_thread::yield() and then tried again. However, this caused the workers to have high CPU usage when idle, as reported by some users. Now, when the worker function cannot find a task to run, it instead sleeps for a duration given by the public member variable sleep_duration (in microseconds) before checking the queue again. The default value is 1000 microseconds, which I found to be optimal in terms of both CPU usage and performance, but your own optimal value may be different.std::thread::hardware_concurrency(), is used instead.timer, which can be used to measure execution time for benchmarking purposes.