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
moduleFoo =letfoo=lazy(ifnot<| bar then
raise <| Exception "Very very very very very very very very very very very very very very long"letret=falseif ret then"foo"else"bar"|> log.Info
ret
)
Result
moduleFoo =letfoo=lazy(ifnot<| bar then
raise
<| Exception "Very very very very very very very very very very very very very very long"letret=falseif ret then"foo"else"bar"|> log.Info
ret)
Problem description
The let ret = false line can't go where it currently is, for indentation reasons. I think the solution in the original code snippet, of putting the bracket on the preceding line and then indenting everything one place, looks best - but possibly worth discussing with other people.
Extra information
[/] The formatted result breaks by code.
The formatted result gives compiler warnings.
I or my company would be willing to help fix this.
We have an easy workaround for this internally: in scope, we've already essentially got Lazy.fromFunc : (unit -> 'a) -> Lazy<'a> which we can use instead.
I'm going to solve the problem of the invalid result in this issue, but I also raised dotnet/docs#24977. So perhaps later, I can circle back if this is also a stylistic bug.
nojaf
added a commit
to nojaf/fantomas
that referenced
this issue
Jul 3, 2021
Issue created from fantomas-online
Code
Result
Problem description
The
let ret = false
line can't go where it currently is, for indentation reasons. I think the solution in the original code snippet, of putting the bracket on the preceding line and then indenting everything one place, looks best - but possibly worth discussing with other people.Extra information
Options
Fantomas Master at 07/01/2021 18:56:12 - 3a12872
Default Fantomas configuration
Did you know that you can ignore files when formatting from fantomas-tool or the FAKE targets by using a .fantomasignore file?
The text was updated successfully, but these errors were encountered: