I’ve recently (~6 months ago) started collecting various slightly useful utility classes and extension methods related to asynchronous programming into a library: AsyncUtilities. Since there are already many useful tools in the BCL and in existing libraries out there these are quite on the fringe:

Utilities:

Extension Methods:

ValueTask

When writing async methods that usually complete synchronously ValueTask<TResult> can be used to avoid allocating a Task<TResult> instance in the synchronous case (I’ve written about it here). There isn’t a non-generic version of ValueTask<TResult> in the BCL. An explanation can be found in the comments for ValueTask<TResult> in the corefx repository:

There is no non-generic version of ValueTask<TResult> as the Task.CompletedTask property may be used to hand back a successfully completed singleton in the case where a Task -returning method completes synchronously and successfully.

However, when you have a tree of async methods without results and they in turn only call methods that return ValueTask<TResult> you need to either allocate Task instances, even if the operations complete synchronously, or you need to remove the async keyword and custom-implement the async mechanism with Task.ContinueWith .

Because I dislike both of these options I made a non-generic ValueTask . Here’s how it can be used:

async ValueTask DrawAsync ( string name ) { var pen = await GetItemAsync < Pen >( "pen" ); var apple = await GetItemAsync < Apple >( "apple" ); var applePen = pen . JamIn ( apple ); applePen . Draw (); } async ValueTask < T > GetItemAsync < T >( string name ) { var item = GetFromCache < T >( name ); if ( item != null ) { return item ; } return await GetFromDbAsync < T >( name ); }

AsyncLock

When awaiting async operations, there’s no thread-affinity (by default). It’s common to start the operation in a certain thread, and resume in another. For that reason, all synchronization constructs that are thread-affine (i.e. match the lock with a specific thread) can’t be used in an async context. One of these is the simple lock statement (which actually uses Monitor.Enter , Monitor.Exit ). For such a case I included AsyncLock which is a simple wrapper over a SemaphoreSlim of 1 (for now, at least):

AsyncLock _lock = new AsyncLock (); async Task ReplaceAsync < T >( string id , T newItem ) { using ( var dbContext = new DBContext ()) { using ( await _lock . LockAsync ()) { await dbContext . DeleteAsync ( id ); await dbContext . InsertAsync ( newItem ); } } }

Striped Lock

Lock striping is a technique used to reduce contention on a lock by splitting it up to multiple lock instances (stripes) with higher granularity where each key is associated with a certain lock/strip (this, for example, is how locks are used inside ConcurrentDictionary to enable higher concurrency). Using a striped lock is similar in practice to using a Dictionary<TKey, TLock> however that forces the number of locks to match the number of keys, while using a striped lock allows to set the concurrency level independently: A higher degree means more granularity but higher memory consumption and vice versa.

Striped

The Striped generic class allows using any kind of lock (with any kind of key). The only necessary things are:

The number of stripes

The lock must have a parameterless constructor, or a delegate for creating it is supplied.

The key must implement GetHashCode and Equals correctly, or an IEqualityComparer<TKey> be supplied.

ThreadSafeCache < string > _cache = new ThreadSafeCache < string >(); Striped < string , object > _lock = Striped . Create < string , object >( Environment . ProcessorCount ); string GetContent ( string filePath ) { var content = _cache . Get ( filePath ); if ( content != null ) { return content ; } lock ( _lock [ filePath ]) { // Double-checked lock content = _cache . Get ( filePath ); if ( content != null ) { return content ; } content = File . ReadAllText ( filePath ); _cache . Set ( content ); return content ; } }

StripedAsyncLock

Since this library is mainly for asynchronous programming, and you can’t use a simple synchronous lock for async methods, there’s also a concrete encapsulation for an async lock. It returns an IDisposable so it can be used in a using scope:

ThreadSafeCache < string > _cache = new ThreadSafeCache < string >(); StripedAsyncLock < string > _lock = new StripedAsyncLock < string >( stripes : 100 ); async Task < string > GetContentAsync ( string filePath ) { var content = _cache . Get ( filePath ); if ( content != null ) { return content ; } using ( await _lock . LockAsync ( filePath )) { // Double-checked lock content = _cache . Get ( filePath ); if ( content != null ) { return content ; } using ( var reader = File . OpenText ( filePath )) { content = await reader . ReadToEndAsync (); } _cache . Set ( content ); return content ; } }

TaskEnumerableAwaiter

TaskEnumerableAwaiter is an awaiter for a collection of tasks. It makes the C# compiler support awaiting a collection of tasks directly instead of calling Task.WhenAll first:

HttpClient _httpClient = new HttpClient (); static async Task DownloadAllAsync () { string [] urls = new [] { "http://www.google.com" , "http://www.github.com" , "http://www.twitter.com" }; string [] strings = await urls . Select ( url => _httpClient . GetStringAsync ( url )); foreach ( var content in strings ) { Console . WriteLine ( content ); } }

It supports both IEnumerable<Task> & IEnumerable<Task<TResult>> and using ConfigureAwait(false) to avoid context capturing. I’ve written about it more extensively here.

CancelableTaskCompletionSource

When you’re implementing asynchronous operations yourself you’re usually dealing with TaskCompletionSource which allows returning an uncompleted task and completing it in the future with a result, exception or cancellation. CancelableTaskCompletionSource joins together a CancellationToken and a TaskCompletionSource by cancelling the CancelableTaskCompletionSource.Task when the CancellationToken is cancelled. This can be useful when wrapping pre async/await custom asynchronous implementations, for example:

Task < string > OperationAsync ( CancellationToken cancellationToken ) { var taskCompletionSource = new CancelableTaskCompletionSource < string >( cancellationToken ); StartAsynchronousOperation ( result => taskCompletionSource . SetResult ( result )); return taskCompletionSource . Task ; } void StartAsynchronousOperation ( Action < string > callback ) { // ... }

Extension Methods:

When implementing low-level async constructs, it’s common to add a small continuation using Task.ContinueWith instead of using an async method (which adds the state machine overhead). To do that efficiently and safely you need the TaskContinuationOptions.ExecuteSynchronously and make sure it runs on the ThreadPool :

Task . Delay ( 1000 ). ContinueWith ( _ => Console . WriteLine ( "Done" ), CancellationToken . None , TaskContinuationOptions . ExecuteSynchronously , TaskScheduler . Default );

TaskExtensions.ContinueWithSynchronously encapsulates that for you (with all the possible overloads):

Task . Delay ( 1000 ). ContinueWithSynchronously ( _ => Console . WriteLine ( "Done" ));

When working with TaskCompletionSource it’s common to copy the result (or exception/cancellation) of another task, usually returned from an async method. TryCompleteFromCompletedTask checks the task’s state and complete the TaskCompletionSource accordingly. This can be used for example when there’s a single worker executing the actual operations one at a time and completing TaskCompletionSource instances that consumers are awaiting:

BlockingCollection < string > _urls = new BlockingCollection < string >(); Queue < TaskCompletionSource < string >> _waiters = new Queue < TaskCompletionSource < string >>(); HttpClient _httpClient = new HttpClient (); async Task DownloadAllAsync () { while ( true ) { await DownloadAsync ( _urls . Take ()); } } async Task DownloadAsync ( string url ) { Task < string > downloadTask = _httpClient . GetStringAsync ( url ); await downloadTask ; TaskCompletionSource < string > taskCompletionSource = _waiters . Dequeue (); taskCompletionSource . TryCompleteFromCompletedTask ( downloadTask ); }

It can sometimes be useful to treat an existing task as a signaling mechanism for cancellation, especially when that task doesn’t represent a specific operation but an ongoing state. ToCancellationTokenSource creates a CancellationTokenSource that gets cancelled when the task completes.

For example, TPL Dataflow blocks have a Completion property which is a task to enable the block’s consumer to await its completion. If we want to show a loading animation to represent the block’s operation, we need to cancel it when the block completes and we know that happened when the Completion task completes: