summaryrefslogtreecommitdiffstats
path: root/clang/lib/Sema/SemaExpr.cpp
diff options
context:
space:
mode:
authorDouglas Gregor <dgregor@apple.com>2009-09-30 21:46:01 +0000
committerDouglas Gregor <dgregor@apple.com>2009-09-30 21:46:01 +0000
commit66950a32d9083727a89ea489b07b90d29f6c9b87 (patch)
tree8509c4754ddee1c92ce98002c177695f464d8312 /clang/lib/Sema/SemaExpr.cpp
parent64c8d5a004cc2f746ed50d0de1401c99b271b054 (diff)
downloadbcm5719-llvm-66950a32d9083727a89ea489b07b90d29f6c9b87.tar.gz
bcm5719-llvm-66950a32d9083727a89ea489b07b90d29f6c9b87.zip
When overload resolution fails for an overloaded operator, show the
overload candidates (but not the built-in ones). We still rely on the underlying built-in semantic analysis to produce the initial diagnostic, then print the candidates following that diagnostic. One side advantage of this approach is that we can perform more validation of C++'s operator overloading with built-in candidates vs. the semantic analysis for those built-in operators: when there are no viable candidates, we know to expect an error from the built-in operator handling code. Otherwise, we are not modeling the built-in semantics properly within operator overloading. This is checked as: assert(Result.isInvalid() && "C++ binary operator overloading is missing candidates!"); if (Result.isInvalid()) PrintOverloadCandidates(CandidateSet, /*OnlyViable=*/false); The assert() catches cases where we're wrong in a +Asserts build. The "if" makes sure that, if this happens in a production clang (-Asserts), we still build the proper built-in operator and continue on our merry way. This is effectively what happened before this change, but we've added the assert() to catch more flies. llvm-svn: 83175
Diffstat (limited to 'clang/lib/Sema/SemaExpr.cpp')
-rw-r--r--clang/lib/Sema/SemaExpr.cpp18
1 files changed, 13 insertions, 5 deletions
diff --git a/clang/lib/Sema/SemaExpr.cpp b/clang/lib/Sema/SemaExpr.cpp
index 2f653b53202..414525d6c33 100644
--- a/clang/lib/Sema/SemaExpr.cpp
+++ b/clang/lib/Sema/SemaExpr.cpp
@@ -1599,11 +1599,19 @@ Sema::ActOnPostfixUnaryOp(Scope *S, SourceLocation OpLoc,
}
}
- case OR_No_Viable_Function:
- // No viable function; fall through to handling this as a
- // built-in operator, which will produce an error message for us.
- break;
-
+ case OR_No_Viable_Function: {
+ // No viable function; try checking this as a built-in operator, which
+ // will fail and provide a diagnostic. Then, print the overload
+ // candidates.
+ OwningExprResult Result = CreateBuiltinUnaryOp(OpLoc, Opc, move(Input));
+ assert(Result.isInvalid() &&
+ "C++ postfix-unary operator overloading is missing candidates!");
+ if (Result.isInvalid())
+ PrintOverloadCandidates(CandidateSet, /*OnlyViable=*/false);
+
+ return move(Result);
+ }
+
case OR_Ambiguous:
Diag(OpLoc, diag::err_ovl_ambiguous_oper)
<< UnaryOperator::getOpcodeStr(Opc)
OpenPOWER on IntegriCloud