The canonical definition of AwaitTaskCorrect is incorrect about equinox HOT 4 CLOSED

I will fix this footgun in user-land. (-__-)

from equinox.

Async.Parallel and AwaitTaskCorrect will never leave an orphan task running.

I can't recall which dotnet/fsharp issue covers this, but the problem here is not AwaitTaskCorrect - it's the fact that the Delay you are invoking is working as spec'd -- delaying forever. Async.Sleep, on the other hand, internally honors cancellation (because it can, via Async.CancellationToken).

Thus I'd claim this is an invalid case - if you replace B with

let B = async {
    let! ct = Async.CancellationToken
    return! Task.Delay(Timeout.Infinite, cancellationToken = ct) |> Async.AwaitTaskCorrect
}

I'm pretty sure Async.AwaitTask shares the same semantics.

from equinox.

Yes, Async.AwaitTask shares the same semantics. Which is why I'd expect AwaitTaskCorrect to improve on the semantics.
It's same story for something based on anything based on TaskCompletionSource.

from equinox.

Leaking unawaited Tasks on every cancellation is an acquired taste; I'd be on the side of preferring the determinism at all costs.
Things like Task.AwaitAll don't do such things
Yes, there is an argument that this can be painful in practice - e.g. like the .NET 4.0 crashing the process if a Task is unobserved, but I think the issues in dotnet/fsharp have traversed this territory far better than we'll ever do here (some are still open - it's definitely not an open and shut thing)

Bottom line in the context of the github/jet repos is that they're all designed to play well with these semantics, e.g. https://github.com/jet/propulsion/blob/master/src/Propulsion/Internal.fs#L68

from equinox.