diff options
| author | David Blaikie <dblaikie@gmail.com> | 2024-06-27 08:17:40 -0700 |
|---|---|---|
| committer | GitHub <noreply@github.com> | 2024-06-27 08:17:40 -0700 |
| commit | a1bce0b89e800cb7ab1d3cf3437f8f34d0695468 (patch) | |
| tree | f11bc059159990336bac56fcd8f40bc0d94870b7 /lldb/source/Plugins/ScriptInterpreter/Python/Interfaces/ScriptedPythonInterface.h | |
| parent | aa24e36d037caee2a4106f721a0ac2ab2a1bc335 (diff) | |
Clang: Add warning flag for storage class specifiers on explicit specializations (#96699)
With the recent fix for this situation in class members (#93873) (for
which the fixed code is invalid prior to this patch - making migrating
code difficult as it must be in lock-step with the compiler migration,
if building with -Werror) it'd be really useful to be able to disable
this warning during the compiler migration/decouple the compiler
migration from the source fixes.
In theory this approach will regress the codebase to the previous
non-member cases of this issue that were already being held back by the
warning (as opposed to if we carved out the new cases into a separate
warning from the existing cases) but I think this'll be so rare and the
cleanup so simple, that the extra regressions of disabling the warning
broadly won't be too much of a problem. (but if folks disagree, I'm open
to making the warning more fine-grained)
Diffstat (limited to 'lldb/source/Plugins/ScriptInterpreter/Python/Interfaces/ScriptedPythonInterface.h')
0 files changed, 0 insertions, 0 deletions
