From the review result:
What's wrong with boost.thread thread_pool was asked somewhere? Well really this type isn't so much a thread pool as an execution context (the base class). I'd suggest renaming to thread_pool_context or threaded_context clears up the confusion here.
Source: Boost review result (conditional acceptance), Boost mailing list, September 2026.
The name is load-bearing: get_system_context() returns thread_pool&, and the type appears throughout the examples and docs. Renaming is a breaking change; options include:
- Rename to
thread_pool_context or threaded_context
- Keep
thread_pool and add an alias
- Keep the name and document the "execution context that owns worker threads" framing where the confusion arises
Related: #395 (type renaming umbrella). If the naming pass there lands, this decision should ride along with it.
From the review result:
Source: Boost review result (conditional acceptance), Boost mailing list, September 2026.
The name is load-bearing:
get_system_context()returnsthread_pool&, and the type appears throughout the examples and docs. Renaming is a breaking change; options include:thread_pool_contextorthreaded_contextthread_pooland add an aliasRelated: #395 (type renaming umbrella). If the naming pass there lands, this decision should ride along with it.