It is not possible to create an Option<Task>.

[NathanMagnus]

It is not possible to create an Option<Task<T>> using .Some.

Both Option.Some(Task<T>) and Option.SomeAsync(Task<T>) produce Task<Option<T>>.

[NathanMagnus]

It appears to be possible using Option.FromNullable(Task) but this not an honest use of the method when the input is known to not be null.

[RyanMarcotte]

I would like to understand the use case better here... What can be accomplished (or made easier by) using Option<Task<T>> that can't with Task<Option<T>>?

[NathanMagnus]

In hindsight, possibly nothing.

It seems a little more accurate when referencing an async call that might not have happened, but doesn't necessarily offer any direct advantages.

[JohannesMoersch]

The problem actually has to do with backward compatibility. There's a Some method that's obsolete that accepts a Task<>. This was from before I introduced the explicit Async methods. Not sure how I can solve this.