Looking at the implementation, it seems that operator safe_bool() and its
companion, operator!(), interrogate whether the referenced fiber has or has
not terminated. joinable() does not.
Add more joinable() cross-references, and cross-reference joinable(), operator
safe_bool() and operator!().
Use [#named_anchor] QuickBook functionality rather than trying to predict the
normalized link for [heading Member function `thread_affinity( bool)`], which
looks like this:
fiber.fiber_mgmt.fiber.member_function__code__phrase_role__identifier__thread_affinity__phrase__phrase_role__special_____phrase___phrase_role__keyword__bool__phrase__phrase_role__special_____phrase___code_
Make condition_variable::wait_until() and wait_for() consistently use 'lk' instead of 'lt' because explanations only describe 'lk'.
Explain condition_variable::wait(), wait_until() and wait_for() Precondition.
Distinguish values returned by wait_until(), wait_for() overloads with and without predicates.
Update request for section concerning algorithm, set_scheduling_algorithm(), round_robin and round_robin_ws.
Clarify lifespan implications of fiber_group::add_fiber(). Explain requirement for a heap fiber object.
Experiment with cross-reference links to other Boost libraries.
