TryAsync prelude should have an overload that takes a Task

[pilotMike]

There is a possible unexpected use case where passing a failed Task into TryAsync can be interpreted as a success:

Since there's no overload taking a Task, the Task goes in to the 'A overload and is interpreted as a success.
There should be something like TryAsync<Unit> TryAsync(Task t) => ...

[louthy]

I realise that usage might be confusing, but there's reasons why I'm not going to change it:

1. I'm planning on deprecating the Async based monadic types. I'm midway through this process on another branch, so making changes to functionality that will be deprecated is just looking for merge headaches that I don't need.
2. Really, as functional programmers, everything should be an expression and therefore everything should return a value. There is an extension to Task called ToUnit() that you should apply to any Task you get from a 3rd party API as soon as you hold the value - it will convert your Task to Task<Unit>. Then make sure all the APIs under your control return values. It's a discipline for sure.

If you still fell that you desperately need this overload: a good technique is to create your own Prelude and then add it a global using static, that will allow you to relatively seamlessly extend the capabilities of LanguageExt without having to manually haul in an extra using for each cs file.

[pilotMike]

Thank you for the reply, that's a good workaround if we need it 👍