#81 pthread rwlock on threadpool information
Closed: Fixed Opened by firstyear.

At the moment we rely on implicit barries in the thread pool config changing. We should remove this assumption through the correct use of rwlocks, which for unblocked reads, are virtually free.


This isn't need, we have barries on the work thread, and __atomic_load's from GCC in #80 to let the shutdown flag be read correctly.

Metadata Update from @firstyear:
- Custom field Origin adjusted to Community
- Custom field Review Status adjusted to review
- Issue close_status updated to: Fixed
- Issue status updated to: Closed (was: Open)

Metadata