forked from OSchip/llvm-project
ad14b5b008
Word on the grapevine was that the committee had some discussion that ended with unanimous agreement on eliminating relational function pointer comparisons. We wanted to be bold and just ban all of them cold turkey. But then we chickened out at the last second and are going for eliminating just the spaceship overload candidate instead, for now. See D104680 for reference. This should be fine and "safe", because the only possible semantic change this would cause is that overload resolution could possibly be ambiguous if there was another viable candidate equally as good. But to save face a little we are going to: * Issue an "error" for three-way comparisons on function pointers. But all this is doing really is changing one vague error message, from an "invalid operands to binary expression" into an "ordered comparison of function pointers", which sounds more like we mean business. * Otherwise "warn" that comparing function pointers like that is totally not cool (unless we are told to keep quiet about this). Signed-off-by: Matheus Izvekov <mizvekov@gmail.com> Reviewed By: rsmith Differential Revision: https://reviews.llvm.org/D104892 |
||
|---|---|---|
| .. | ||
| expr.arith.conv | ||
| expr.ass | ||
| expr.cast | ||
| expr.cond | ||
| expr.const | ||
| expr.mptr.oper | ||
| expr.post | ||
| expr.prim | ||
| expr.unary | ||
| p3.cpp | ||
| p8.cpp | ||
| p9.cpp | ||
| p10-0x.cpp | ||
| p13.cpp | ||