Re: [Boost-bugs] [Boost C++ Libraries] #10128: Use lockable_adapter with const objects or const members

Subject: Re: [Boost-bugs] [Boost C++ Libraries] #10128: Use lockable_adapter with const objects or const members
From: Boost C++ Libraries (noreply_at_[hidden])
Date: 2014-07-04 05:53:05

#10128: Use lockable_adapter with const objects or const members
-------------------------------+----------------------
  Reporter:  anonymous         |      Owner:  viboes
      Type:  Feature Requests  |     Status:  assigned
 Milestone:  To Be Determined  |  Component:  thread
   Version:  Boost 1.54.0      |   Severity:  Problem
Resolution:                    |   Keywords:
-------------------------------+----------------------

Comment (by viboes):

 After more thoughts, I have some doubts. I'm not sure it is correct to
 make these lock/unlock functions const. These functions are public making
 the nested mutex a salient attribute.

 It would be different is the mutex was not salient. E.g.
 synchronized_value wraps a type and makes the synchronized mutex not
 salient. Please, could you see if you can use synchronized_value instead?

-- 
Ticket URL: <https://svn.boost.org/trac/boost/ticket/10128#comment:4>
Boost C++ Libraries <http://www.boost.org/>
Boost provides free peer-reviewed portable C++ source libraries.