One thought that hits me right now: should we use ConfigureAwait(false) everywhere?
Because this is a reusable library which could be consumed by an app model which has a custom SynchronizationContext and/or a non-default TaskScheduler.
But we can omit it in the Terminal-Test and the Unit-Tests.
One thought that hits me right now: should we use
ConfigureAwait(false)
everywhere? Because this is a reusable library which could be consumed by an app model which has a customSynchronizationContext
and/or a non-defaultTaskScheduler
. But we can omit it in the Terminal-Test and the Unit-Tests._Originally posted by @Flash0ver in https://github.com/TimoHeiten/zer0mqXt/pull/29#discussion_r615489988_