https://bugs.llvm.org/show_bug.cgi?id=48196
Bug ID: 48196
Summary: improve diagnostic for "new func()"
Product: clang
Version: unspecified
Hardware: PC
OS: Linux
Status: NEW
Severity: enhancement
Priority: P
Component: -New Bugs
Assignee: [email protected]
Reporter: [email protected]
CC: [email protected], [email protected],
[email protected], [email protected]
Testcase:
class Foo {
Foo() = default;
public:
static Foo make();
};
Foo *test() {
return new Foo::make();
}
Clang emits:
<source>:8:19: error: no type named 'make' in 'Foo'
return new Foo::make();
~~~~~^
1 error generated.
Compiler returned: 1
Which was quite confusing at first. There is a 'make' in 'Foo'. Once I
confirmed that, I read the message again. Why does clang demand a type, it's
not like I said typename? What is going on. The error doesn't point at the real
bug, the extra 'new'.
In general when emitting a diagnostics with "there is no X named Y in Z" please
point out that there is a Y in Z that isn't an X. Also when possible please
point to the reason why we're expecting a type (in this case, the 'new'). In
this specific case, it would be magical if clang tried to typo-correct removing
'new' to see if the function call expression would parse and produce an
expression of the correct type.
--
You are receiving this mail because:
You are on the CC list for the bug._______________________________________________
llvm-bugs mailing list
[email protected]
https://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-bugs