public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
* [Bug c++/94152] New: Mistyped destructor name diagnostic suboptimal
@ 2020-03-12 10:34 rguenth at gcc dot gnu.org
2020-03-12 11:24 ` [Bug c++/94152] " redi at gcc dot gnu.org
0 siblings, 1 reply; 2+ messages in thread
From: rguenth at gcc dot gnu.org @ 2020-03-12 10:34 UTC (permalink / raw)
To: gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=94152
Bug ID: 94152
Summary: Mistyped destructor name diagnostic suboptimal
Product: gcc
Version: 10.0
Status: UNCONFIRMED
Severity: enhancement
Priority: P3
Component: c++
Assignee: unassigned at gcc dot gnu.org
Reporter: rguenth at gcc dot gnu.org
Target Milestone: ---
struct _X { ~_X(); };
_X::~X () {}
produces
t.C:2:8: error: expected class-name before ‘(’ token
_X::~X () {}
^
where clang says
t.C:2:6: error: expected the class name after '~' to name a destructor
_X::~X () {}
^
_X
which is clearly better.
^ permalink raw reply [flat|nested] 2+ messages in thread
* [Bug c++/94152] Mistyped destructor name diagnostic suboptimal
2020-03-12 10:34 [Bug c++/94152] New: Mistyped destructor name diagnostic suboptimal rguenth at gcc dot gnu.org
@ 2020-03-12 11:24 ` redi at gcc dot gnu.org
0 siblings, 0 replies; 2+ messages in thread
From: redi at gcc dot gnu.org @ 2020-03-12 11:24 UTC (permalink / raw)
To: gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=94152
Jonathan Wakely <redi at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Last reconfirmed| |2020-03-12
Ever confirmed|0 |1
Status|UNCONFIRMED |NEW
^ permalink raw reply [flat|nested] 2+ messages in thread
end of thread, other threads:[~2020-03-12 11:24 UTC | newest]
Thread overview: 2+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2020-03-12 10:34 [Bug c++/94152] New: Mistyped destructor name diagnostic suboptimal rguenth at gcc dot gnu.org
2020-03-12 11:24 ` [Bug c++/94152] " redi at gcc dot gnu.org
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).