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
Mine is concerned with fn calls though. I'd say for calls, the generally better choice is quite clear. For data/defs (such as your example) there's more room for subjectivity.
In your example, I'd prefer the former as:
it frees up more horizontal space to be used (one may use e.g. 80 characters max)
it's data. I'd say it's great to have different styles for code and data. Once one follows this consistently, visual scanning of codebases becomes a pleasure
I think I've seen way more usages of the first style in the wild. Someone has to check this, though. Generally I don't have any issues with recommending this in the guide.
Should Clojurists favour narrow formatting with top-level forms on new lines, like this:
Or wider formatting that avoids splitting forms with line breaks unless they extend beyond 80 characters, like this?
I find the first version easier to scan but don't see any general advice in the guide about this.
The text was updated successfully, but these errors were encountered: