Shifted Quote

[IgorErin]

Issue created from fantomas-online

Code

let unionTests context =
    [ ptestProperty (message "GenericDU<bool, Option<bool>>")
      <| fun (data: GenericDU<bool, Option<bool>>[]) ->

          testProperty (message "GenericRecord<Option<int>, Option<int64>>")
          <| fun (data: GenericRecord<Option<int>, Option<int64>>[]) ->
              if data.Length <> 0 then
                  check data
                  <| fun length ->
                      <@
                          fun (range: Range1D) (buffer: ClArray<_>) ->
                              ()

                      @> ]

Result

let unionTests context =
    [ ptestProperty (message "GenericDU<bool, Option<bool>>")
      <| fun (data: GenericDU<bool, Option<bool>>[]) ->

          testProperty (message "GenericRecord<Option<int>, Option<int64>>")
          <| fun (data: GenericRecord<Option<int>, Option<int64>>[]) ->
              if data.Length <> 0 then
                  check data
                  <| fun length ->
                      <@ fun (range: Range1D) (buffer: ClArray<_>) -> ()

                      @> ]

Problem description

Fantomas himself says that this result requires formatting

Extra information

• [ ] The formatted result breaks my code.
• [ ] The formatted result gives compiler warnings.
• [ ] I or my company would be willing to help fix this.
• [ ] I would like a release if this problem is solved.

Options

Fantomas main branch at 1/1/1990

Default Fantomas configuration

_{Did you know that you can ignore files when formatting by using a .fantomasignore file? PS: It's unlikely that someone else will solve your specific issue, as it's something that you have a personal stake in.}

[nojaf]

Hello, thank you for showing interest in this project.

The online tool actually formats the code twice and verifies the first formatted result is idempotent. As it is not reporting such a problem, I'm not sure there is a problem here.

Two things might be happening:

• You are on an older version of Fantomas and the problem no longer occurs on the latest main.
• You didn't enter any settings that are required to draw out the problem.

Could you verify these things, please?