If library consumer is using coroutines, there should be an API for creating an Event.Observer that leverages the use of CoroutineScope to create its own OnEvent.Executor, as well as unsubscribe itself from any Processor via CoroutineScope.invokeOnCompletion handler.
If library consumer is using coroutines, there should be an API for creating an
Event.Observerthat leverages the use ofCoroutineScopeto create its ownOnEvent.Executor, as well as unsubscribe itself from anyProcessorviaCoroutineScope.invokeOnCompletionhandler.