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
It might be hard to come up with a consistent rule for this. Nevertheless I think the former is much easier to read (and doesn't eat a whole page in my editor)
It's tough to say when a list should be formatted with one line per element versus many elements per line. One (kind of clunky) way around this is to concatenate a bunch of sub-lists. For example:
Yeah, that is quite clunky and not necessarily without runtime overhead or a clarity cost.
Perhaps a neat way of allowing the user to signal the wrapping would be to break after the first empty comment in the list and at multiples of that index, for example:
This would allow the user to select the wrapping in a low visual overhead way. I think that clang format has some similar behaviour, at the very least I remember using empty comments to force wrapping of lists when they'd usually be put on one line.
Not quite sure how discoverable this is, but perhaps that ok as this is probably a niche issue anyway.
If it had to be done without hints from the programmer I'd say that lists should be:
On one line if possible.
One line per element if any element is itself "long" (for some threshold to bikeshed, perhaps as small as 4 or 5 characters).
As square as possible with as few elements as possible on the last line.
It might be hard to come up with a consistent rule for this. Nevertheless I think the former is much easier to read (and doesn't eat a whole page in my editor)
The text was updated successfully, but these errors were encountered: