| ▲ | smoothdeveloper 3 days ago |
| In C#, you can't use the await keyword in a non async method, so I find the argument short sighted. |
|
| ▲ | shortrounddev2 3 days ago | parent | next [-] |
| I don't see how that changes things. You'd have to async it all the way to the top but the syntax is still cleaner than F#. If you're using an Asp.Net controller you just declare the handler as async Task<IActionResult> and it's fine. Even program main methods can be async these days |
| |
| ▲ | malakai521 2 days ago | parent [-] | | The syntax is exactly the same. You have `var x = await` in C# and `let! x =` in F# The controller handler is also the same. It will be marked with `async` keyword in C# and `task` CE in F# | | |
| ▲ | shortrounddev2 2 days ago | parent [-] | | It's absolutely not exactly the same; let! is only available within a computation block. If you want to return some value from the computation block and return to Functional land without having to pause the thread you need to use a continuation, which C# has built in syntactic sugar for in async/await and F# does not. | | |
| ▲ | sparkie 2 days ago | parent | next [-] | | `await` can only be used in an `async` function. How is that so different from `let!` only being available in a computation expression? | | |
| ▲ | shortrounddev2 2 days ago | parent [-] | | because an async function doesn't require you to change syntaxes to get them to work | | |
| ▲ | Smaug123 2 days ago | parent [-] | | It's actually sort of the other way round. C# has hardcoded syntax for async/await. F#'s syntax for async/await is a fully-general user-accessible mechanism. | | |
| ▲ | sparkie 2 days ago | parent [-] | | They're not so different in that regard. C# `await` can be adapted by making an awaitable and awaiter type[1], which isn't to dissimilar to how a computation expression in F# needs to implement methods `Bind`, `Return`, `Yield`, etc. In both languages these patterns make up for the absence of typeclasses to express things like a functor, applicative, monad, comonad, etc. [1]https://ecma-international.org/wp-content/uploads/ECMA-334_7... |
|
|
| |
| ▲ | xigoi 2 days ago | parent | prev [-] | | A computation block is the equivatent of an async function; |
|
|
|
|
| ▲ | jayd16 3 days ago | parent | prev [-] |
| If your code base is already using async await it's really not an issue. |
| |
| ▲ | int_19h 2 days ago | parent [-] | | The point is that it's not actually different from C#, especially once you consider that F# also has task{} blocks that give you a .NET Task directly. |
|
