This commit updates Seq.Api to follow best practice of calling ConfigureAwait(false) for non-UI libraries/non-top level code. At the top level code, like SeqTail, a developer would NOT specify ConfigureAwait(false) and the continuation of the async method would be marshaled back to the synchronization context captured before the await.
Hi Nick,
This commit updates Seq.Api to follow best practice of calling ConfigureAwait(false) for non-UI libraries/non-top level code. At the top level code, like SeqTail, a developer would NOT specify ConfigureAwait(false) and the continuation of the async method would be marshaled back to the synchronization context captured before the await.
Here's some references: Async/Await - Best Practices in Asynchronous Programming Preventing the Deadlock Stackoverflow