[hansvm]

I'll use a warning if it might be an error but I don't have enough information to be certain (most commonly when I'm trying to infer essential information about a compilation target and have a reasonable but fallible fallback for esoteric targets).

That leaves the caller of my library in control of how they want to handle such cases:

(1) If they silence warnings then everything will probably still work.

(2) If they convert warnings to errors then they can immediately inspect that warning and see how it applies to their use case. They might still just silence the warning, or they might add in some kind of override or shim so that my code works on their system.