diff options
| author | Joe Loser <joeloser93@gmail.com> | 2021-10-05 14:08:42 -0400 |
|---|---|---|
| committer | Joe Loser <joeloser93@gmail.com> | 2021-10-05 14:08:48 -0400 |
| commit | 8cf5319affc2441c2901908140c14f7153078199 (patch) | |
| tree | be7fd3e99ce87fbeb780e2bdc8314325767dde0b /lldb/test/Shell/ScriptInterpreter/Python | |
| parent | d5a4c86d14488baee9c42c45b27c3addb8877624 (diff) | |
| download | llvm-8cf5319affc2441c2901908140c14f7153078199.zip llvm-8cf5319affc2441c2901908140c14f7153078199.tar.gz llvm-8cf5319affc2441c2901908140c14f7153078199.tar.bz2 | |
[libc++][test] Use = delete over DELETE_FUNCTION. NFC.
Some tests repeat the definition of `DELETE_FUNCTION` macro locally.
However, it's not even requred to guard against in the C++03 case since
Clang supports `= delete;` in C++03 mode. A warning is issued but
`libc++` tests run with `-Wno-c++11-extensions`, so this isn't an issue.
Since we don't support other compilers in C++03 mode, `= delete;` is
always available for use. As such, inline all calls of `DELETE_FUNCTION`
to use `= delete;`.
Reviewed By: ldionne, #libc
Differential Revision: https://reviews.llvm.org/D111148
Diffstat (limited to 'lldb/test/Shell/ScriptInterpreter/Python')
0 files changed, 0 insertions, 0 deletions