You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
By convention, space is added when applying functions to tupled arguments:
165
+
In default formatting conventions, a space is added when applying lower-case functions to tupled or parenthesized arguments:
166
+
166
167
```fsharp
167
168
// OK
168
-
someFunction1 (x.IngredientName, x.Quantity)
169
+
someFunction2 ()
170
+
171
+
// OK
172
+
someFunction3 (x.Quantity1 + x.Quantity2)
169
173
170
-
// OK, but formatting tools will add the extra space by default
171
-
someFunction1(x.IngredientName, x.Quantity)
174
+
// Not OK, formatting tools will add the extra space by default
175
+
someFunction2()
176
+
177
+
// Not OK, formatting tools will add the extra space by default
178
+
someFunction3(x.IngredientName, x.Quantity)
172
179
```
173
180
174
-
For capitalized methods accepting tupled arguments, no space is added. This is because these are often used with fluent programming:
181
+
In default formatting conventions, no space is added when applying capitalized methods to tupled arguments. This is because these are often used with fluent programming:
175
182
176
183
```fsharp
177
-
// OK - Methods accepting tuples are applied without a space:
184
+
// OK - Methods accepting parenthesize arguments are applied without a space
185
+
SomeClass.Invoke()
186
+
187
+
// OK - Methods accepting tuples are applied without a space
178
188
String.Format(x.IngredientName, x.Quantity)
179
189
180
-
// OK - it's important not to use a space if using fluent programming with chained '.' invocations
0 commit comments