Allow undentation in method and constructor calls

I propose we allow undentation in method and constructor calls without emitting a warning.

The existing way of approaching this problem in F# is that the arguments need to be placed more on the right side of the equal and the caller subject.

Sample:

This is possible today:

let x = System.DateTime(
            year = 2020,
            month = 12,
            day = 1)

also this:

let x =
    System.DateTime(
        year = 2020,
        month = 12,
        day = 1)

and:

let x =
    System.DateTime(
        year = 2020,
        month = 12,
        day = 1
    )

This gives a warning (FS0058):

let x = System.DateTime(
    year = 2020,
    month = 12,
    day = 1)

and likewise:

let x = System.DateTime(
    year = 2020,
    month = 12,
    day = 1
)

also this gives a warning (but is okay in constructors via dotnet/fsharp#6808):

let x = System.DateTime(year = 2020,
    month = 12,
    day = 1)

Sidenote:

Also this way of defining constructors or methods gives a warning:

type Foo (
    y: int,
    x: int) =
    member self.Bar(
        a: int,
        b: int) =
        ()

but this is okay:

type Foo (y: int,
    x: int) =
    member self.Bar(a: int,
        b: int) =
        ()

which was mentioned in #724 (comment) but apparently didn't made it into the PR...

Pros and Cons

The advantages of making this adjustment to F# is a visually more pleasant way of calling methods. Style and elegance is a very subjective view but it goes hand in hand with the relaxed indentation for lists and arrays introduced in F# 4.5 and the "elmish" style formatting.

The disadvantages of making this adjustment to F# are: (too much?) choices!

Extra information

Estimated cost (XS, S, M, L, XL, XXL): S?

Related suggestions: (put links to related suggestions here)

Affidavit (please submit!)

Please tick this by placing a cross in the box:

• This is not a question (e.g. like one you might ask on stackoverflow) and I have searched stackoverflow for discussions of this issue
• I have searched both open and closed suggestions on this site and believe this is not a duplicate
• This is not something which has obviously "already been decided" in previous versions of F#. If you're questioning a fundamental design decision that has obviously already been taken (e.g. "Make F# untyped") then please don't submit it.

Please tick all that apply:

• This is not a breaking change to the F# language design
• I or my company would be willing to help implement and/or test this

For Readers

If you would like to see this issue implemented, please click the 👍 emoji on this issue. These counts are used to generally order the suggestions by engagement.