[all-commits] [llvm/llvm-project] 91354f: [C++20] Destroying delete can cause a type to be n...

[Aaron Ballman via All-commits]

  Branch: refs/heads/main
  Home:   https://github.com/llvm/llvm-project
  Commit: 91354fb1469620cc92c4bf1a11444b2e7f13d54d
      https://github.com/llvm/llvm-project/commit/91354fb1469620cc92c4bf1a11444b2e7f13d54d
  Author: Aaron Ballman <aaron at aaronballman.com>
  Date:   2024-12-05 (Thu, 05 Dec 2024)

  Changed paths:
    M clang/docs/ReleaseNotes.rst
    M clang/lib/Sema/SemaExceptionSpec.cpp
    A clang/test/SemaCXX/noexcept-destroying-delete.cpp

  Log Message:
  -----------
  [C++20] Destroying delete can cause a type to be noexcept when deleting (#118687)

Given a `noexcept` operator with an operand that calls `delete`, Clang
was not considering whether the selected `operator delete` function was
a destroying delete or not when inspecting whether the deleted object
type has a throwing destructor. Thus, the operator would return `false`
for a type with a potentially throwing destructor even though that
destructor would not be called due to the destroying delete. Clang now
takes the kind of delete operator into consideration.

Fixes #118660



To unsubscribe from these emails, change your notification settings at https://github.com/llvm/llvm-project/settings/notifications