Boost C++ Libraries: Ticket #6640: interprocess::named_condition::wait interruption point https://svn.boost.org/trac10/ticket/6640 <p> boost::thread has defined interruption points, one of which is boost::condition_variable::wait(). </p> <p> what about interprocess::named_condition::wait(), </p> <p> how should one interrupt a thread waiting on a named_condition? </p> <p> shouldn't interprocess::named_condition::wait() also be an interruption point! </p> en-us Boost C++ Libraries /htdocs/site/boost.png https://svn.boost.org/trac10/ticket/6640 Trac 1.4.3 megaposer Thu, 30 Jul 2015 12:23:54 GMT <link>https://svn.boost.org/trac10/ticket/6640#comment:1 </link> <guid isPermaLink="false">https://svn.boost.org/trac10/ticket/6640#comment:1</guid> <description> <p> It would be great to have this feature available. </p> <p> Right now I am doing a busy-loop with a 100 ms timed_wait() and a check on an std::atomic&lt;bool&gt; whether there has been an interrupt. This is more than unsatisfactory. </p> <p> I understand that a proper implementation for this is difficult to achieve, especially if one wants to interrupt a very specific thread limited to the current process. </p> </description> <category>Ticket</category> </item> <item> <dc:creator>Ion Gaztañaga</dc:creator> <pubDate>Thu, 30 Jun 2016 20:33:29 GMT</pubDate> <title>status changed; resolution set https://svn.boost.org/trac10/ticket/6640#comment:2 https://svn.boost.org/trac10/ticket/6640#comment:2 <ul> <li><strong>status</strong> <span class="trac-field-old">new</span> → <span class="trac-field-new">closed</span> </li> <li><strong>resolution</strong> → <span class="trac-field-new">wontfix</span> </li> </ul> <p> The implementation of interruption points for process-shared synchronization primitives would be really hard to achieve and it's not required by standard C++ mutexes. So closing it as wontfix. </p> Ticket