Don Syme

@0x53A thanks for taking the time to reply. I'd love to have more data points. Can you link your code?

> The need for this is there, for example there are a bunch of proposals on https://github.com/dotnet/csharplang asking for this exact thing: dotnet/csharplang#2542 Yes indeed! Thanks for this link :-)

F# has a few obscure open-able modules that very fe people end up using. Does anyone really do open Checked or open NullableOperators or open NonStructuralComparison ? I think these...

> is that the same yes > nor any docs on a NonStructuralComparison module. Some docs are here, but yes it should be in the language reference. https://fsharp.github.io/fsharp-core-docs/reference/fsharp-core-operators-nonstructuralcomparison.html

Another option is to have both "task {...}" and "backgroundTask {...}" Though I find it frustrating that using ConfigureAwait(false) for backgroundTask still starts the task in the current thread, up...

> How much would the thread pool switch hurt scenarios where the awaited value is immediately available? It would hurt in micro samples. However it just seems such a shame...

Any comments on `backgroundTask { ... }`? Naming? Also there's a possibility we'll add `valueTask { ... }` or `vtask { ... }` (though it sort of requires a .NET...

My plan is to implement `backgroundTask { .. }` like this: ``` type BackgroundTaskBuilder() = inherit TaskBuilderBase() member inline this.Run(code : TaskCode) : Task

> I don't know how big this penalty is, but I'm surprised that it is considered acceptable since performance has been such a high priority in task support work as...

Hmmm. First, for `backgroundTask`, the `Delay` is removed and `Task.Run` is now used instead, see [here](https://github.com/dotnet/fsharp/blob/feature/tasks/src/fsharp/FSharp.Core/tasks.fs#L207). I'm not sure if that makes a difference to your analysis. Note that, currently,...