I don't think it's a gopls issue. Rather, it's the unfortunate default behavior of VS Code. There's an option editor.comments.ignoreEmptyLines to toggle comments even for empty lines:

Thanks for finding that, @ShoshinNikita! @jsoref, does that resolve the issue for you?

I guess? It seems like it's designed for this use case (and applies evenly across the platform).

I pretty much never use this feature (perhaps because I've never trusted an IDE to be remotely smart, and this reenforces that opinion). (I tried it because colleagues were using it, and I needed to perform a routine task of isolating test cases until I could figure out which ones were failing.) (I'm actually quite impressed w/ VSC in general, and am using it to replace Notepad or similar.)

I expect I'm more likely to not use the comment-lines feature at all and return to manually adding /*...*/ around blocks.

Ok, thanks for following up. Looks like this setting resolves the issue, so I will close this, as well as the upstream issue.

I think this issue also covers that there is no folding range for block comments /* .. */ (which is also available as a command in VS Code), which could be addressed in gopls:

Change https://golang.org/cl/325071 mentions this issue: internal/lsp: fix folding range for block comments