CODEWITHSUNDEEP
gocoding-styleconventions
orcaman
orcaman

Reputation: 6551

Golang Coding Conventions: When to Break Lines in Code?

One of my favorite things about go is gofmt. I like the fact that the coding style is standardized in many ways.

However there is one thing that bothers me still: line breaks. I found that if I look at my company's codebase, there is no evident consistency on the question of when to break lines.

Looking at some of the code in the stdlib, for example, the fmt code here, I'm still not sure what's the convention (if it exists at all).

For example, on fmt_integer function here, there are line breaks after if statement bodies, but on fmt_sbx here there aren't.

Is there a convention for line breaks in golang? what's considered best practice?

Upvotes: 3

Views: 7140

Answers (1)

VonC
VonC

Reputation: 1323125

First, there will be at most one empty line after an if block (because of go fmt).

Second, adding or not an extra blank line does not follow any hard rule, except code readability.

It is not even mentioned in the "Go Code Review Comments" wiki page.

Upvotes: 5

Related Questions