Whether a setting belongs to Fantomas rather than to editorconfig itself or to another tool. Matched without regard to case, as editorconfig matches keys.

Whether a value is one the editorconfig spec gives a meaning that is not a value. `unset` says a setting from a parent file no longer applies, `indent_size = tab` says to follow `tab_width`, and `max_line_length = off` says there is no limit. Fantomas keeps its default for them without reporting a problem: they are not mistakes, and the library derives `indent_size = tab` on its own from `indent_style = tab`, so reporting them blames an author for something they never wrote. The setting and the value are both matched without regard to case, as editorconfig matches them. Only these exact values are excused. Anything else, `indent_size = banana` included, is a mistake and is reported like any other.

The supported setting closest to `setting`, when one is within `limit` edits of it. Two candidates the same distance away are separated by the order of `supportedSettings`.

Read a `FormatConfig` from editorconfig properties, falling back to `fallbackConfig` for anything the properties do not set. Keys and values are both matched without regard to case, as editorconfig defines them, and when two keys fold onto one the last wins. Returns the settings it could not act on alongside the configuration, each named the way it was written, so the caller can decide whether and how to report them.

Every setting of a configuration, under the name it is written with and with its value spelled the way an `.editorconfig` would carry it, in record field order.

Every .editorconfig setting this build of Fantomas understands, in the order they are worth reading: the settings editorconfig itself defines first, then the ones belonging to Fantomas, each group ordered without regard to case. The former keep their upstream names and are not prefixed, the latter all carry the `fsharp_` prefix.