forked from OSchip/llvm-project
5c1399a582
Implement support for try-catch blocks in constexpr functions, as proposed in http://wg21.link/P1002 and voted in San Diego for c++20. The idea is that we can still never throw inside constexpr, so the catch block is never entered. A try-catch block like this: try { f(); } catch (...) { } is then morally equivalent to just { f(); } Same idea should apply for function/constructor try blocks. rdar://problem/45530773 Differential Revision: https://reviews.llvm.org/D55097 llvm-svn: 348789 |
||
---|---|---|
.. | ||
analyzer | ||
demo | ||
OpenProjects.html | ||
UniversalDriver.html | ||
builtins.py | ||
carbon-compile.png | ||
clang_video-05-25-2007.html | ||
clang_video-07-25-2007.html | ||
comparison.html | ||
compatibility.html | ||
content.css | ||
cxx_compatibility.html | ||
cxx_dr_status.html | ||
cxx_status.html | ||
diagnostics.html | ||
favicon.ico | ||
feature-compile1.png | ||
feature-compile2.png | ||
feature-memory1.png | ||
features.html | ||
get_involved.html | ||
get_started.html | ||
hacking.html | ||
index.html | ||
libstdc++4.4-clang0x.patch | ||
libstdc++4.6-clang11.patch | ||
libstdc++4.7-clang11.patch | ||
make_cxx_dr_status | ||
menu.css | ||
menu.html.incl | ||
related.html | ||
robots.txt |