aboutsummaryrefslogtreecommitdiff
path: root/lldb/packages/Python/lldbsuite/test/gdbclientutils.py
diff options
context:
space:
mode:
authorVictor Chernyakin <chernyakin.victor.j@outlook.com>2025-09-04 10:32:56 -0700
committerGitHub <noreply@github.com>2025-09-04 10:32:56 -0700
commitbcb3bd09275f833a76d1122f59d4b49b52c8d299 (patch)
tree9dbc13b4cc0b0c4d7bc66be615fa1091813f009b /lldb/packages/Python/lldbsuite/test/gdbclientutils.py
parentbdb9283eec633585a14f7b1640822448c17ed71a (diff)
downloadllvm-bcb3bd09275f833a76d1122f59d4b49b52c8d299.zip
llvm-bcb3bd09275f833a76d1122f59d4b49b52c8d299.tar.gz
llvm-bcb3bd09275f833a76d1122f59d4b49b52c8d299.tar.bz2
[clang-tidy] Raise minimum standard level for several checks from C++98 to C++11 (#152401)
`modernize-replace-auto-ptr`, `modernize-use-equals-delete`, and `modernize-use-auto` use `std::unique_ptr`, `= delete`, and `auto` respectively, which are all C++11 features. The interesting bit is `modernize-use-nullptr`'s tests: - Some relied on int-to-pointer conversions that were removed in C++11. There are two variations here. First, tests like this, which become ill-formed: ```cpp const int null = 0; void * ptr = null; ``` I just deleted these cases; if they're ill-formed, we're not losing anything, right? Second, tests like this: ```cpp float * ptr = (float *)int(0.f); ``` These don't become ill-formed, but start generating a different AST. In C++98, they are `NullToPointer` conversions, but in C++11, they become generic `IntegralToPointer` conversions. I deleted these cases too, though I'm less sure here. - Folded `struct Bar` into `class A`, because those both suffer from the same false negatives.
Diffstat (limited to 'lldb/packages/Python/lldbsuite/test/gdbclientutils.py')
0 files changed, 0 insertions, 0 deletions