https://gcc.gnu.org/bugzilla/show_bug.cgi?id=116178
--- Comment #9 from Sam James <sjames at gcc dot gnu.org> --- (In reply to Sam James from comment #8) To give another example where it might be useful: ICU often ends up cranking the C++ standard its headers expect before its consumers have bumped it, recently this was w/ C++17. OK. pkg-config doesn't encode this information, so we have to manually go around with packaging and make things build with C++17. All these "append-flags -std=c++17" lines become stale at some point when the compiler switches from using C++14 to C++17 by default in $compiler, or when the package finally catches up. At least with saying "just use the latest" we wouldn't be building packages with something silently older as a workaround. I appreciate these are kind of niche and a bit out there though.
