aboutsummaryrefslogtreecommitdiff
path: root/lldb/source/Commands/CommandObjectFrame.cpp
diff options
context:
space:
mode:
authorDouglas Gregor <dgregor@apple.com>2011-01-25 22:19:32 +0000
committerDouglas Gregor <dgregor@apple.com>2011-01-25 22:19:32 +0000
commit407371a1e4dd7b43d620e71b09429c236ac0ce47 (patch)
tree7eccc83c2fc0c56f3dbdfc6bb0ea0ff7b65021e1 /lldb/source/Commands/CommandObjectFrame.cpp
parent7e1ec9ccd8bf572234b97bd6ac7a4be5aeddf38d (diff)
downloadllvm-407371a1e4dd7b43d620e71b09429c236ac0ce47.zip
llvm-407371a1e4dd7b43d620e71b09429c236ac0ce47.tar.gz
llvm-407371a1e4dd7b43d620e71b09429c236ac0ce47.tar.bz2
Speculatively implement a tweak to the C++0x overload resolution rules
for reference binding (C++ [over.rank.ics]p3b1sb4), so that we prefer the binding of an lvalue reference to a function lvalue over the binding of an rvalue reference. This change resolves the ambiguity with std::forward and lvalue references to function types in a way that seems consistent with the original rvalue references proposal. My proposed wording for this change is shown in isBetterReferenceBindingKind(); we'll try to get this change adopted in the C++0x working paper as well. llvm-svn: 124236
Diffstat (limited to 'lldb/source/Commands/CommandObjectFrame.cpp')
0 files changed, 0 insertions, 0 deletions