Same as rpp::subjects::replay_subject but on_next/on_error/on_completed calls are serialized via mutex. More...

#include <replay_subject.hpp>

Additional Inherited Members
Public Types inherited from rpp::subjects::details::replay_subject_base< Type, true >
using	optimal_disposables_strategy

Public Member Functions inherited from rpp::subjects::details::replay_subject_base< Type, true >
	replay_subject_base (size_t count)

	replay_subject_base (size_t count, rpp::schedulers::duration duration)

auto	get_observer () const

auto	get_observable () const

rpp::disposable_wrapper	get_disposable () const

Detailed Description

template<rpp::constraint::decayed_type Type>
class rpp::subjects::serialized_replay_subject< Type >

Same as rpp::subjects::replay_subject but on_next/on_error/on_completed calls are serialized via mutex.

When you are using ordinary rpp::subjects::replay_subject, then you must take care not to call its on_next method (or its other on methods) in async way.

See also: https://reactivex.io/documentation/subject.html

The documentation for this class was generated from the following files:

src/rpp/rpp/subjects/fwd.hpp
src/rpp/rpp/subjects/replay_subject.hpp

Additional Inherited Members

Detailed Description