Ben S.The #SonarLint extension for #vscode is super-helpful for encouraging modern C++ best-practices, but it has a serious flaw: It doesn't take into account some complex situations (e.g. class member initialization involving opaque types), and there doesn't seem to be a way to suppress warnings on a line-by-line basis.
Adding a `//NOSONAR` comment is supposed to work, but support was apparently removed because it because it's too heavy-handed - it disables *all* findings on a given line.
I've seen chatter about a more fine-grained approach, but apparently everyone was still waiting as of late last year.
This is really annoying because my IDE is now full of noise that I have to sift through to find actual legitimate concerns.