aboutsummaryrefslogtreecommitdiff
path: root/clang/lib/Frontend/CompilerInvocation.cpp
diff options
context:
space:
mode:
authorArthur O'Dwyer <arthur.j.odwyer@gmail.com>2020-12-25 16:22:54 -0500
committerArthur O'Dwyer <arthur.j.odwyer@gmail.com>2021-01-08 17:33:13 -0500
commit963b771e24caff502d6b5d9b2f72dd88dd56e97a (patch)
tree4eac573dd21e9aa8919256425255640cf7286a43 /clang/lib/Frontend/CompilerInvocation.cpp
parentca1694b9d07cf14dd15d804b37fa151f4e082c2f (diff)
downloadllvm-963b771e24caff502d6b5d9b2f72dd88dd56e97a.zip
llvm-963b771e24caff502d6b5d9b2f72dd88dd56e97a.tar.gz
llvm-963b771e24caff502d6b5d9b2f72dd88dd56e97a.tar.bz2
[libc++] Mark [P0475] "LWG2511: guaranteed copy elision for piecewise construction" as Complete.
The point of LWG2511 is basically just to make sure that we use `tuple<Args&&...>` instead of `tuple<Args...>` in a couple of places inside `scoped_allocator_adaptor` and inside `pair`. As far as I can tell, this has been true for libc++ since EricWF's D27612 (and maybe even earlier than that).
Diffstat (limited to 'clang/lib/Frontend/CompilerInvocation.cpp')
0 files changed, 0 insertions, 0 deletions