Ticket #2361 (closed Feature Requests: fixed)
thread_specific_ptr: nature of the key, complexity and rationale
|Reported by:||vicente.botet@…||Owned by:||viboes|
|Version:||Boost 1.36.0||Severity:||Not Applicable|
I didn't know that the key of thread_specific_ptr was the address of the variable. I expected a constant complexity for boost::thread_specific_ptr, but if the key is the address this seams not possible. I supose you had some good raison to not use an index key instead of the address.
Please, could you add the nature of the key, the complexity of the boost::thread_specific_ptr and the rationale on the design choice on the documentation.
Ticket requested by A. W. on http://www.nabble.com/-thread--TSS-cleanup-to19590361.html#a19623640
- Owner changed from anthonyw to viboes
- Status changed from new to assigned
- Milestone changed from Boost 1.37.0 to To Be Determined