0bde483bd2
Introduce private push_(), try_push_(), push_wait_until_() helper methods: each of push(), try_push() and push_wait_until() has two signatures for value_type const& versus value_type&&, but the code paths are identical once we have a new node_type in hand. Moreover, extract processing common to all into private push_and_notify_() method. (This fixes an inconsistency in push() exception behavior.) Extract common processing from pop(), value_pop(), try_pop() and pop_wait_until() to private value_pop_() method. This retains a node_type::ptr to the old head node until return time, unifying the code paths between its return-by-value and assign-through-reference callers. (This fixes an inconsistency in try_pop() exception behavior.)
boost.fiber
boost.fiber provides a framework for micro-/userland-threads (fibers) scheduled cooperativly. The API contains classes and functions to manage and synchronize fibers similiar to boost.thread.
A fiber is able to store the current execution state, including all registers and CPU flags, the instruction pointer, and the stack pointer and later restore this state. The idea is to have multiple execution paths running on a single thread using a sort of cooperative scheduling (threads are preemptively scheduled) - the running fiber decides explicitly when its yields to allow another fiber to run (context switching).
A context switch between threads costs usally thousends of CPU cycles on x86 compared to a fiber switch with less than 100 cycles. A fiber can only run on a single thread at any point in time.
Building: Detailed instructions can be found at https://svn.boost.org/trac/boost/wiki/TryModBoost.