Lines Matching full:notify

91             virtual void notify() noexcept = 0;
141 [member_link algorithm..notify] is called [mdash] whichever comes first.
142 The interaction with `notify()` means that, for instance, calling
148 round_robin..notify].]]
149 [[Note:] [Given that `notify()` might be called from another thread, your
152 your `notify()` implementation.]]
155 [member_heading algorithm..notify]
157         virtual void notify() noexcept = 0;
162 [[Note:] [Alone among the `algorithm` methods, `notify()` may be called
163 from another thread. Your `notify()` implementation must guard any data it
186             virtual void notify() noexcept;
234 [member_heading round_robin..notify]
236         virtual void notify() noexcept = 0;
281             virtual void notify() noexcept;
342 [member_heading work_stealing..notify]
344         virtual void notify() noexcept = 0;
385             virtual void notify() noexcept;
446 [member_heading shared_work..notify]
448         virtual void notify() noexcept = 0;
487             void notify() noexcept;
503 [member_heading fiber_properties..notify]
505         void notify() noexcept;
521 method should call `notify()` once the new property value has been stored.
525 behavior of the `pick_next()` method, you need not call `notify()` when that
551             virtual void notify() noexcept = 0;
606 [member_heading algorithm_with_properties..notify]
608         virtual void notify() noexcept = 0;
613 [[Note:] [same as [member_link algorithm..notify]]]
637 [[Effects:] [Notify the custom scheduler of a possibly-relevant change to a
643 fiber_properties..notify].]]
970 [member_link algorithm..notify] is called to wake it up.]]