Details
Diff Detail
- Repository
- rG LLVM Github Monorepo
Event Timeline
| clang/lib/Sema/SemaOverload.cpp | ||
|---|---|---|
| 14105 | It is a bit sad that the broken function call cases (too many/few agguments) are failing into this group, all candidates are not viable -- this means we don't get any benefits (no Best), for some cases, it is suboptimal even though the best candidate looks like obvious. class Collection {
const char *find(int) const;
char* find(int);
};
void test1(const Collection &C) {
C.find(); // we want const char*, but all overloads are not viable and return types are not the same, so no type captured here.
} | |
| clang/lib/Sema/SemaOverload.cpp | ||
|---|---|---|
| 14083 | seems like bool Success = false would be a "safer" default and have to be set in fewer places | |
| 14105 | Yeah, at some point we can add more heuristics (discard non-viable or hidden functions using heuristics) to handle this case, like I did in SemaCodeComplete... | |
| 14133 | resolvation -> resolution | |
| clang/test/AST/ast-dump-recovery.cpp | ||
| 123 | why does this not work? | |
sorry for the delay, picking it up now.
| clang/lib/Sema/SemaCoroutine.cpp | ||
|---|---|---|
| 864 ↗ | (On Diff #308267) | we need this change to prevent a regression on co_await-range-for. without this change, we will emit 2 call to deleted member function 'await_transform' diagnostics on https://github.com/llvm/llvm-project/blob/master/clang/test/SemaCXX/co_await-range-for.cpp#L52-L54. |
| clang/test/AST/ast-dump-recovery.cpp | ||
| 123 | this is on a different codepath, will fix in https://reviews.llvm.org/D92298 | |
seems like bool Success = false would be a "safer" default and have to be set in fewer places