Consider relaxing ASTTransformer treatment of ranges in record fields

[Smaug123]

As used in Myriad, SynExprRecordField requires a range in the second argument (the "where is the equals sign" range, mEq) or else the conversion to an Oak will result in having no fields in the record due to

fantomas/src/Fantomas.Core/ASTTransformer.fs

Line 979 in fc341e8

| SynExprRecordField((fieldName, _), Some mEq, Some expr, _) ->

. (So currently you end up with { } instead of a record with any fields, if you didn't supply the equals range.)

Would it be reasonable to treat None the same as Some range0 here? (That's what I've done in my client code and it seems to be fine.)

[nojaf]

Hi there, similar requests have come up with this in the past.
Fantomas expects a valid syntax tree, as the parser would produce.
We don't want to take any requests to process imperfect syntax trees.
This is somewhat mentioned in the docs.