Reorganze WaitForIdle() methods to reduce code duplication
@rockfordlhotka
During the changes I've become unhappy with the currenty WaitForIdle() structure, because a user would now have to override two methods to get consistent behavior. The methods with TimeSpan and CancellationToken because the first throws a TimeoutException and the latter a TaskCanceledException. I understand why both implementation use different exceptions but from a user perspective it's awkward to override two methods to have consistent behavior. Any ideas?
@rockfordlhotka During the changes I've become unhappy with the currenty
WaitForIdle()structure, because a user would now have to override two methods to get consistent behavior. The methods withTimeSpanandCancellationTokenbecause the first throws aTimeoutExceptionand the latter aTaskCanceledException. I understand why both implementation use different exceptions but from a user perspective it's awkward to override two methods to have consistent behavior. Any ideas?