Async support

[fbouvard]

Hi,
How about adding Task SwitchAsync() to make void Switch() awaitable for example ?
Instead of taking Action<T>, it would take Action<Task<T>>.

[SalmanAerovative]

why has this issue been closed?
Edit: for anyone else looking for switchasync, use match which returns task

[fbouvard]

why has this issue been closed? Edit: for anyone else looking for switchasync, use match which returns task

There is already this opened PR. Never got merged

[emperador-ming]

why has this issue been closed? Edit: for anyone else looking for switchasync, use match which returns task

Yes. We use OneOf intensively and since an async conditional branch makes mandatory for every other conditional branch to return a Task, Task.FromResult becomes ubiquitously painful.

[SalmanAerovative]

Yes. We use OneOf intensively and since an async conditional branch makes mandatory for every other conditional branch to return a Task, Task.FromResult becomes ubiquitously painful.

How do you handle async lambdas? right now i am managing with Match but with this method also, we have to do the painful Task.FromResult or Task.CompletedTask

[mcintyre321]

I generally just mark the lambdas as async.

…

On Tue, 23 Jan 2024, 13:18 SalmanAerovative, ***@***.***> wrote: Yes. We use OneOf intensively and since an async conditional branch makes mandatory for every other conditional branch to return a Task, Task.FromResult becomes ubiquitously painful. How do you handle async lambdas? right now i am managing with Match but with this method also, we have to do the painful Task.FromResult or Task.CompletedTask — Reply to this email directly, view it on GitHub <#136 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AACDJ6WI27AJJWSQMSUBZU3YP62CBAVCNFSM6AAAAAATOXK5WOVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTSMBWGA2DENZSHA> . You are receiving this because you are subscribed to this thread.Message ID: ***@***.***>

[emperador-ming]

Yes. We use OneOf intensively and since an async conditional branch makes mandatory for every other conditional branch to return a Task, Task.FromResult becomes ubiquitously painful.

How do you handle async lambdas? right now i am managing with Match but with this method also, we have to do the painful Task.FromResult or Task.CompletedTask

Yeah. We use Match & Task.FromResult, the same as you do.

[emperador-ming]

I generally just mark the lambdas as async.
…
On Tue, 23 Jan 2024, 13:18 SalmanAerovative, @.> wrote: Yes. We use OneOf intensively and since an async conditional branch makes mandatory for every other conditional branch to return a Task, Task.FromResult becomes ubiquitously painful. How do you handle async lambdas? right now i am managing with Match but with this method also, we have to do the painful Task.FromResult or Task.CompletedTask — Reply to this email directly, view it on GitHub <#136 (comment)>, or unsubscribe https://github.com/notifications/unsubscribe-auth/AACDJ6WI27AJJWSQMSUBZU3YP62CBAVCNFSM6AAAAAATOXK5WOVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTSMBWGA2DENZSHA . You are receiving this because you are subscribed to this thread.Message ID: @.>

From a practical point of view, this is probably the best option. Nevertheless, the resulting warning CS1998: 'This async method lacks await operators...' is annoying.