> ref parameters I actually like the way F# does refs more! byref<'T> aligns more closely with internal compiler terminology and makes it more clear that this

> ref parameters I actually like the way F# does refs more! byref<'T> aligns more closely with internal compiler terminology and makes it more clear that this is something like a pointer. Having to perform tupled calls over curried is indeed an annoyance, and even a bigger one is the prevalent fluent style which results in thing |> _.InstanceMethod1() |> _.InstanceMethod2() |> _.Build() Ugh, I usually try to shuffle around what I find annoying into bespoke functions (which are thankfully very easy to define) or even declaring operators. It also helps that while selection is not vast, F# tends to have various libraries that either provide alternatives or wrap existing widely adopted packages into a more functional F#-native API e.g. Oxpecker, Avalonia FuncUI, FSharp.Data, etc.