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
I'm not entirely sure about this one but here goes:
To tackle fsprojects/fantomas#495, if I remember correctly, we internally aligned on how the GR way of solving this bug would be.
I think the part of having the = on a separate line was proposed by you folks.
Could we add a section on how long functions should be formatted?
The thing I'm after here is to know what the rule is about indenting the rest of the function after the function name.
For example:
letsomeName(a :int)(b :int):int=// start of function
a + b
My question is about the spaces before (a : int), are they one indentation length (4 spaces in this example), or do the align the start of someName?
If the indentation is 4 spaces they are one and the same.
Related Fantomas bug: fsprojects/fantomas#883
The text was updated successfully, but these errors were encountered:
So I'm guessing the fix in Fantomas should be focussed on one indentation.
I opened the question on how to format long signatures at the Microsoft style guide.
They might see things differently than how GR would do it.
So maybe it is a good idea to add this guide as well?
I'm not entirely sure about this one but here goes:
To tackle fsprojects/fantomas#495, if I remember correctly, we internally aligned on how the GR way of solving this bug would be.
I think the part of having the
=
on a separate line was proposed by you folks.Could we add a section on how long functions should be formatted?
The thing I'm after here is to know what the rule is about indenting the rest of the function after the function name.
For example:
My question is about the spaces before
(a : int)
, are they one indentation length (4 spaces in this example), or do the align the start ofsomeName
?If the indentation is 4 spaces they are one and the same.
Related Fantomas bug: fsprojects/fantomas#883
The text was updated successfully, but these errors were encountered: