https://bugs.llvm.org/show_bug.cgi?id=40576
Bug ID: 40576
Summary: Clang should turn destroying delete off by default.
Product: clang
Version: trunk
Hardware: PC
OS: All
Status: NEW
Severity: normal
Priority: P
Component: C++2a
Assignee: [email protected]
Reporter: [email protected]
CC: [email protected], [email protected],
[email protected], [email protected]
Defining new names in namespace `std` is technically a non-conforming
extensions. This makes it difficult for libc++ to backport C++20 destroying
delete.
Currently Clang unconditionally defines `__cpp_impl_destroying_delete`. Unlike
aligned allocation or sized deallocation which can be turned on or off by user.
I believe we should make destroying delete act similarly. We should provide
flags for enabling destroying delete prior to C++17. After
`__cpp_impl_destroying_delete` should be defined by default.
Lets also consider whether Clang should provide destroying delete as an
extension prior to C++20.
PS. I'm concerned that if Clang always provides destroying delete but libc++
doesn't define it until C++20, then users will be dinks and define their own
`std::destroying_delete_t` as a workaround.
--
You are receiving this mail because:
You are on the CC list for the bug._______________________________________________
llvm-bugs mailing list
[email protected]
https://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-bugs
