interprocess::named_condition::wait interruption point

[David Akehurst <david.akehurst@…>]

boost::thread has defined interruption points, one of which is boost::condition_variable::wait().

what about interprocess::named_condition::wait(),

how should one interrupt a thread waiting on a named_condition?

shouldn't interprocess::named_condition::wait() also be an interruption point!

[megaposer]

It would be great to have this feature available.

Right now I am doing a busy-loop with a 100 ms timed_wait() and a check on an std::atomic<bool> whether there has been an interrupt. This is more than unsatisfactory.

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.

[Ion Gaztañaga]

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.