Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>(1) I don't see any reason that signalling a condition variable has to be guarded by a mutex, from a data-race stand-point. Obviously, you have the possibility of receiving redundant notifications or losing notifications, but if this is an acceptable or recoverable error condition for your program, I don't believe there's anything in the standard that will make it illegal. The standard, of course, won't guard you against race conditions; it's the programmer's responsibility to make sure that race conditions are benign. (And, of course, it is essential that the programmer not put any "data races", which are defined very specifically in the standard but don't apply directly to synchronization primitives, or undefined behavior is summoned.)</p> <p>(2) I can't answer a question like this about the internal implementation of a standard library facility. It is, of course, the vendor's responsibility to provide library facilities that work correctly and meet the specification. This library's implementation may have some internal state that requires mutual exclusion to avoid corruption, or it may perform locking in order to avoid lost or redundant notifications. (Just because your program may tolerate them, doesn't mean arbitrary users of the library can, and in general I expect they can't.) It would just be speculation on my part what they're guarding with this mutex.</p> <p>(3) <code>condition_variable_any</code> is made to work on any lock-like object, while <code>condition_variable</code> is designed specifically to work with <code>unique_lock&lt;mutex&gt;</code>. The latter is probably easier to implement and/or more performant than the former, since it knows specifically which types it is operating on and what they require (whether they're trivial, whether they fit in a cache line, whether they map directly to a specific platform's set of syscalls, what fences or cache coherence guarantees they imply, etc.), while the former provides a generic facility for operating on lock-ish objects without being stuck specifically with the constraints of <code>std::mutex</code> or <code>std::unique_lock&lt;&gt;</code>.</p>
    singulars
    1. This table or related slice is empty.
    1. PODo I need to synchronize std::condition_variable/condition_variable_any::notify_one
      singulars
      1. PTQuestion
    1. PTAnswer
    1. This table or related slice is empty.
    1. USAdam H. Peterson
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    2. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    1. COPerhaps I should add to Q: implementation of condition_variable_any is just thin wrapper around condition_variable+mutex.
      singulars
      1. PO
      1. USqble
    2. CO"Just because your program may tolerate them, doesn't mean arbitrary users of the library can, and in general I expect they can't" - I think you don't get my point - if I don't guard my notify_one by mutex by myself - there can be lost notifications, but if I guard it - they should be impossible. Implementation should not care about lost notifications when user don't protects notify_one by mutex.
      singulars
      1. PO
      1. USqble
    3. CO@qble: Again, I can't really comment on what a standard library vendor chooses to do to implement their implementation of the standard. They're allowed to use whatever compiler magic to get it to work (including undefined behavior, if they happen to know that their platform defines it) and they can take advantage of very specific knowledge. It could be that they know that std::lock_guard<std::mutex> acts atomically enough for them, but the types associated with the template parameters may not. You might find a clue in their implementation of wait().
      singulars
      1. PO
      1. USAdam H. Peterson
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload