Re:Why F#?
by shortrounddev2 on Tuesday April 01, 2025 @11:42AM
(#43548150)
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.
[ Parent
| on HN ]
`await` can only be used in an `async` function. How is that so different from `let!` only being available in a computation expression?
Re:Why F#?
by shortrounddev2 on Tuesday April 01, 2025 @12:40PM
(#43548847)
because an async function doesn't require you to change syntaxes to get them to work
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.
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...