I see your point, and agree it might be painful. it depends on the promises the maintainer makes to themselves and to their users. I'd rather break the build a

I see your point, and agree it might be painful. it depends on the promises the maintainer makes to themselves and to their users. I'd rather break the build and get immediately alerted by (hopefully moderately) upset downstream packagers than having this warning become visible in my users builds. It isn't just about getting rid of a warning, but the new compiler has changed some important logic so this warning might highlight potentially undefined behavior. Am I, the maintainer OK with that - that is the main question I believe. Might be useful to do regression with any new compiler being released especially when a product is used in safety or security critical systems.