[PATCH] D113517: Correct handling of the 'throw()' exception specifier in C++17.

[Richard Smith - zygoloid via Phabricator via cfe-commits]

rsmith added a comment.

What's the motivation for this change? I believe the current behavior is still conforming: `set_unexpected` is no longer (officially) part of the standard library (though it still exists as a zombie name), and the default `unexpected` handler calls `terminate`, so calling `unexpected` rather than `terminate` should have the same effect, except in non-conforming programs that call `std::set_unexpected` anyway. Do we generate better code if we call `terminate` rather than `unexpected`?


Repository:
  rG LLVM Github Monorepo

CHANGES SINCE LAST ACTION
  https://reviews.llvm.org/D113517/new/

https://reviews.llvm.org/D113517