The second factor is the continued evolution and development of the Fantomas package, which is an F# code formatter tool. Having this in place is an important step towards bringing some level of consistency to the formatting.

Firstly, there's a set of official F# Style Guidelines that's been developed along with a set of issues around this.

As such, code formatters have become more and more popular over the years to the extent that some languages have them built in as a code part of the language - Elm being one example of that.į# doesn't have a built-in or pervasive code formatter, although this is starting to slowly change thanks to a few developments. On the one hand there's nothing necessarily wrong with that, but on the other hand one can make the argument that it's something that shouldn't be an issue or need any thought expended on it. There are certainly some patterns that we see most teams that we work with adopting, but in other cases there's a wide degree of variance. Code formatting is something that - at least currently - in F# is somewhat of a subjective matter.

Visual studio code formatting