Related: #187.

I wonder how much effort is it to implement with staticcheck.io

It should be fairly simple to implement a check that flags the code. Adding an automated suggested fix would be problematic due to the way go/ast handles comments.

However, it won't be a high priority for me in the near future, as I want to concentrate on correctness issues for the time being, not stylistic ones.

This is pretty straightforward to implement with ruleguard or semgrep.

Edit:

rules:
  - id: loop-nesting
    patterns:
    - pattern: |
              for ... {
                if ... {
                  ...
                }
              }
    message: "reduce nesting in loop with continue"
    languages: [go]
    severity: ERROR

Edit: So I ran this on all the Go code on my machine and basically triggered nothing but false positives. Probably there needs to be some logic to ignore blocks with 'break' or 'return' in the indented body, and maybe a minimum indented body length.

@dominikh great that you agree this check is simple. I'll see if I can find time to make a PR