diff options
| author | Douglas Gregor <dgregor@apple.com> | 2011-01-25 19:39:31 +0000 |
|---|---|---|
| committer | Douglas Gregor <dgregor@apple.com> | 2011-01-25 19:39:31 +0000 |
| commit | 1c5a53e200c29b44907318ea22e31c0ae50f3d57 (patch) | |
| tree | f364c42e4ff820874d07f0fdd8b632329e427ae7 /clang/lib/Frontend/CompilerInvocation.cpp | |
| parent | ade45d97038e907f94e9d9492f6b5cec58d3563c (diff) | |
| download | bcm5719-llvm-1c5a53e200c29b44907318ea22e31c0ae50f3d57.tar.gz bcm5719-llvm-1c5a53e200c29b44907318ea22e31c0ae50f3d57.zip | |
Fix the ranking of reference bindings during overload resolution
(C++0x [over.ics.rank]p3) when one binding is an lvalue reference and
the other is an rvalue reference that binds to an rvalue. In
particular, we were using the predict "is an rvalue reference" rather
than "is an rvalue reference that binds to an rvalue", which was
incorrect in the one case where an rvalue reference can bind to an
lvalue: function references.
This particular issue cropped up with std::forward, where Clang was
picking an std::forward overload while forwarding an (lvalue)
reference to a function. However (and unfortunately!), the right
answer for this code is that the call to std::forward is
ambiguous. Clang now gets that right, but we need to revisit the
std::forward implementation in libc++.
llvm-svn: 124216
Diffstat (limited to 'clang/lib/Frontend/CompilerInvocation.cpp')
0 files changed, 0 insertions, 0 deletions
