5 ms·

You don't really. F# has the task{} abstraction that works just like C# and is fully compatible.

• hansvm 2y ago
  Which works fine assuming all new development is happening in the F# half of a codebase and you don't have a significant amount of old F# async code lying around.
  • phillipcarter 2y ago
    It doesn't require that. You can do a strangler pattern of sorts and use task for the interop layer, then run each call site through a small helper that converts to F# async. Or, hell, just throw caution to the wind and text replace. I've heard some folks do that and it worked out well for them + wasn't much time to clean up either. They're especially happy to have better stack traces too.
    • hansvm 2y ago
      So...it _does_ require that, but if you have time/risk to spare then there exist tenable migration strategies.