Issues

Issues

• Laying out an infix expression that does not fit on one line

  fsharp/fslang-design#836 · opened on Aug 27, 2026
  5

• [style-guide] do! indents

  fsharp/fslang-design#793 · opened on Jan 23, 2025
  2

• [style-guide]: Multiline generic type parameters bracket alignment

  fsharp/fslang-design#756 · opened on Nov 13, 2023
  3

• [style-guide] Treat cast operators :> and :?> as pipe operators

  fsharp/fslang-design#737 · opened on May 19, 2023

• [style-guide] Lambda closing paren defaults

  fsharp/fslang-design#730 · opened on Feb 21, 2023
  5

• [style-guide] Breaking of complex pattern match expressions

  fsharp/fslang-design#725 · opened on Dec 26, 2022
  1

• [style-guide] Multiline application in patterns

  fsharp/fslang-design#717 · opened on Nov 3, 2022
  2

• [style-guide] Parameter owner patterns should be consistent with prefix application expressions

  fsharp/fslang-design#712 · opened on Sep 26, 2022
  10

• [style-guide] prefer leading rather than trailing operators

  fsharp/fslang-design#687 · opened on Jul 5, 2022
  10

• [style-guide] Formatting of argument lists

  fsharp/fslang-design#664 · opened on May 25, 2022
  27

• [style-guide] Format mutation expressions on their own line

  fsharp/fslang-design#663 · opened on May 18, 2022
  11

• [style-guide] when expressions in match clauses

  fsharp/fslang-design#662 · opened on May 18, 2022
  15

• [style-guide] space around SynType.StaticConstantExpr

  fsharp/fslang-design#657 · opened on Mar 4, 2022
  3

• [style-guide] Vanity alignment used when using long case in match block

  fsharp/fslang-design#647 · opened on Oct 25, 2021
  26

• Question about operators starting with ?

  fsharp/fslang-design#639 · opened on Oct 24, 2021
  3

• [style-guide] Better control of pattern match handlers and line breaks.

  fsharp/fslang-design#650 · opened on Nov 20, 2018
  34