Format let and in on a single line if they fit #97
No reviewers
Labels
No Label
blocked: dependency
blocked: info-needed
bug
duplicate
enhancement
fixed in HEAD
help wanted
hs:arrows
hs:brackets
hs:classes
hs:comments
hs:do-notation
hs:guards
hs:lists
hs:operators
hs:patterns
hs:records
hs:types
invalid
language extension support
layouting
needs confirmation
priority: high
priority: low
question
revisit before next release
wontfix
No Milestone
No project
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: hexagoxel/brittany#97
Loading…
Reference in New Issue
There is no content yet.
Delete Branch "let-in-on-single-lines"
Deleting a branch is permanent. Although the deleted branch may exist for a short time before cleaning up, in most cases it CANNOT be undone. Continue?
This addresses #73
The following is wasteful of vertical space:
We should format it on two lines if possible.
This commit also allows for a mix of variations:
uhm,
appSep
should append a separator (space) if required. SoappSep "in "
is redundant, and also there should be no reason not to unconditionally useappSep
here. (and i realize this was not introduced by this diff - the same redundancy was in the before-state.)Or was there some issue around a comment following
in
?.. lets just test. could you try if replacingifIndentLeftElse id appSep $ docLit $ Text.pack "in "
withappSep $ docLit $ Text.pack "in"
works?looks good (otherwise)!
Shooting from the hip here, but maybe this makes xxx and yyy line up in
?
I'd check, but my network connection won't really let me at present.
@chreekat oh, right. I missed that detail. I guess then this is fine.
thanks!
Thanks for finishing this one off @lspitzner