How to use FusionTasks with CancellationToken in F#?

FusionTasks handles CancellationToken implicitly in async workflows via Async.DefaultCancellationToken. For explicit control, use the AsAsync method with a token, but it's not directly integrable with let!/do! as per the README's TIPS on manual conversion outside async blocks.

FusionTasks vs manual Async.AwaitTask conversion: which is better?

FusionTasks reduces boilerplate by allowing direct Task usage in F# async, ideal for seamless integration. Manual conversions offer more control and avoid dependencies, so choose based on whether you prioritize convenience or minimalism in your codebase.

Does FusionTasks support .NET 7 or later versions?

The README states version 2.6.0 is 'final' and ready for F# 7.0, but since it's marked as the last release, future .NET versions might not be officially supported. Check the GitHub repository for any community updates or forks.

How to handle IAsyncEnumerable in F# with FusionTasks?

Simply use the for expression in an async block with IAsyncEnumerable , and FusionTasks handles asynchronous iteration. Ensure your .NET environment supports it, as it requires net461 or higher due to dependency on Microsoft.Bcl.AsyncInterfaces.

What are the performance implications of using FusionTasks?

FusionTasks aims for low-overhead conversions and minimizes allocations for completed tasks. However, the appendix notes that ValueTask may have limited performance benefits in F# contexts, so benchmark if performance is critical in chatty scenarios.

Is FusionTasks still actively maintained?

The project is declared 'final version' in the history, suggesting no further major updates. It's stable for current .NET and F# versions, but for long-term projects, consider this lack of active maintenance when evaluating future compatibility.

FSharp.Control.FusionTasks — F# Async & .NET Task Interop

What is FSharp.Control.FusionTasks?

FSharp.Control.FusionTasks is a library that enables seamless interoperability between F#'s Async workflows and .NET's Task/ValueTask models. It allows F# developers to directly await .NET Tasks within async blocks and lets C# developers await F# Async computations, solving the friction when mixing asynchronous code across these two .NET languages.

Target Audience

F# and C# developers working on mixed-language codebases, library authors who need to expose async APIs consumable from both languages, and teams integrating .NET OSS packages that use Task/ValueTask into F# projects.

Value Proposition

It provides a lightweight, intuitive bridge between the two async models without requiring manual boilerplate conversions, supports modern async features like IAsyncEnumerable and ValueTask, and works across a wide range of .NET platforms from .NET Framework 4.5 to .NET 6.

F# Async workflow <--> .NET Task/ValueTask easy seamless interoperability library.

Use Cases

Best For

Calling .NET library async methods (Task/ValueTask) directly from F# async workflows
Exposing F# async computations to C# code as awaitable Tasks
Building mixed F#/C# applications with shared asynchronous logic
Using IAsyncEnumerable<T> sequences within F# async for loops
Integrating with .NET OSS packages that expose Task-based APIs in F# projects
Writing LINQPad scripts that combine F# async and .NET Task operations

Not Ideal For

Projects relying on custom 'task-like' async types beyond Task and ValueTask, as FusionTasks only supports standard .NET async models.
Scenarios requiring explicit, fine-grained control over CancellationToken propagation in F# async workflows, since it relies on implicit handling.
Environments targeting .NET versions below 4.6.1 or .NET Standard 1.6 where IAsyncEnumerable support is unavailable, limiting feature use.
Teams prioritizing minimal dependencies for async interoperability, preferring manual conversions or built-in F# tools over third-party libraries.

Pros & Cons

Pros

Seamless Task Integration

Allows direct use of Task/ValueTask with let!, do!, and use! in F# async blocks, eliminating manual Async.AwaitTask conversions as shown in sample code for MemoryStream operations.

Bidirectional Interoperability

Enables C# code to await F# Async computations directly, simplifying mixed-language projects without extra boilerplate, demonstrated in C# sample code awaiting FSharpAsync.Sleep.

Modern Async Feature Support

Integrates IAsyncEnumerable<T> in F# for loops and IAsyncDisposable in use expressions, supporting .NET's latest asynchronous patterns as highlighted in the features list.

Wide Platform Compatibility

Works across .NET Framework 4.5 to .NET 6, F# 4.5 to 6.0, and various .NET Core versions, ensuring broad applicability as detailed in the environments chart.

Cons

Limited to Standard Async Types

Cannot support arbitrary 'task-like' types beyond Task and ValueTask due to .NET limitations, restricting use with custom async models as explained in the appendix.

Implicit CancellationToken Handling

In F# async workflows, CancellationToken is handled implicitly, which may not suit scenarios needing explicit token propagation, as noted in the README's TIPS section on manual conversion.

Requires Type Annotations

Compiler conflicts between Async and Task types can necessitate type annotations in async workflows, adding complexity as mentioned in the TIPS section with FS0041 errors.

Dependency on External Packages

For IAsyncEnumerable support, it relies on Microsoft.Bcl.AsyncInterfaces, introducing an extra dependency and limiting compatibility to specific .NET versions as outlined in the notes.

Frequently Asked Questions

What is FSharp.Control.FusionTasks?

Target Audience

Value Proposition

Use Cases

Best For

Calling .NET library async methods (Task/ValueTask) directly from F# async workflows
Exposing F# async computations to C# code as awaitable Tasks
Building mixed F#/C# applications with shared asynchronous logic
Using IAsyncEnumerable<T> sequences within F# async for loops
Integrating with .NET OSS packages that expose Task-based APIs in F# projects
Writing LINQPad scripts that combine F# async and .NET Task operations

Not Ideal For

Projects relying on custom 'task-like' async types beyond Task and ValueTask, as FusionTasks only supports standard .NET async models.
Scenarios requiring explicit, fine-grained control over CancellationToken propagation in F# async workflows, since it relies on implicit handling.
Environments targeting .NET versions below 4.6.1 or .NET Standard 1.6 where IAsyncEnumerable support is unavailable, limiting feature use.
Teams prioritizing minimal dependencies for async interoperability, preferring manual conversions or built-in F# tools over third-party libraries.

Pros & Cons

Pros

Seamless Task Integration

Allows direct use of Task/ValueTask with let!, do!, and use! in F# async blocks, eliminating manual Async.AwaitTask conversions as shown in sample code for MemoryStream operations.

Bidirectional Interoperability

Enables C# code to await F# Async computations directly, simplifying mixed-language projects without extra boilerplate, demonstrated in C# sample code awaiting FSharpAsync.Sleep.

Modern Async Feature Support

Integrates IAsyncEnumerable<T> in F# for loops and IAsyncDisposable in use expressions, supporting .NET's latest asynchronous patterns as highlighted in the features list.

Wide Platform Compatibility

Works across .NET Framework 4.5 to .NET 6, F# 4.5 to 6.0, and various .NET Core versions, ensuring broad applicability as detailed in the environments chart.

Cons

Limited to Standard Async Types

Cannot support arbitrary 'task-like' types beyond Task and ValueTask due to .NET limitations, restricting use with custom async models as explained in the appendix.

Implicit CancellationToken Handling

In F# async workflows, CancellationToken is handled implicitly, which may not suit scenarios needing explicit token propagation, as noted in the README's TIPS section on manual conversion.

Requires Type Annotations

Compiler conflicts between Async and Task types can necessitate type annotations in async workflows, adding complexity as mentioned in the TIPS section with FS0041 errors.

Dependency on External Packages

For IAsyncEnumerable support, it relies on Microsoft.Bcl.AsyncInterfaces, introducing an extra dependency and limiting compatibility to specific .NET versions as outlined in the notes.

Frequently Asked Questions

FSharp.Control.FusionTasks

What is FSharp.Control.FusionTasks?

Overview

Use Cases

Best For

Not Ideal For

Pros & Cons

Pros

Cons

Frequently Asked Questions

Related Projects

Found a gem we're missing?

FSharp.Control.FusionTasks

What is FSharp.Control.FusionTasks?

Overview

Use Cases

Best For

Not Ideal For

Pros & Cons

Pros

Cons

Frequently Asked Questions

Related Projects

Found a gem we're missing?