Warning: Some posts on this platform may contain adult material intended for mature audiences only. Viewer discretion is advised. By clicking ‘Continue’, you confirm that you are 18 years or older and consent to viewing explicit content.
Welcome to F# Weekly, A roundup of F# content from this past week: News Generate Local .NET Secrets from Azure Deployments – .NET Blog (microsoft.com) Get started with .NET 8 and AI using new…
I love F#, and use it all the time, but I really don’t care for how async was implemented. Do other people feel the same? It just feels like it was tacked on with all these “!” keywords.
I guess that’s fair, I was thinking more of how you have to convert dotnet tasks into f# async, and the nomenclature around “Async.RynSyncronously” vs something like “Async.await”
I love F#, and use it all the time, but I really don’t care for how async was implemented. Do other people feel the same? It just feels like it was tacked on with all these “!” keywords.
It’s a Computation Expression - a core feature of the language since very early, and it’s pretty amazing IMO and not only used for async/task
I guess that’s fair, I was thinking more of how you have to convert dotnet tasks into f# async, and the nomenclature around “Async.RynSyncronously” vs something like “Async.await”