Another option is to disable the warning locally [...] But this is compiler-specific and noisy. It also does not explain the real issue to anyone reading the code.

I don't understand this logic. Surely disabling the warning is directly explaining the actual issue, that the code emits a false positive warning for specific compilers and conditions? That the false_but_compiler_does_not_know_it_ thing is apparently the better way to convey what's going on seems kind of ridiculous.

I disagree on the naming of 'compiler-tricks'. Some of us are complete idiots and prefer the compiler trick US

​^(^​^N^​^o^​^t^​^t^​^h^​^e^​^o^​^t^​^h^​^e^​​^r^​^w^​^a^​^y^​^a^​^r^​^o^​^u^​^n^​^d^​^.^​^)^

Good read!

A small UI issue: the screenshot appear in darkmode but I could find how to trigger the dark mode in the website.