public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "mpolacek at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c++/97531] New: Improve type/non-type declaration diagnostic Date: Thu, 22 Oct 2020 15:27:26 +0000 [thread overview] Message-ID: <bug-97531-4@http.gcc.gnu.org/bugzilla/> (raw) https://gcc.gnu.org/bugzilla/show_bug.cgi?id=97531 Bug ID: 97531 Summary: Improve type/non-type declaration diagnostic Product: gcc Version: 11.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: c++ Assignee: unassigned at gcc dot gnu.org Reporter: mpolacek at gcc dot gnu.org Target Milestone: --- For this: struct A { }; struct B { B(A); }; void fn () { B(A()); // extern struct B A (void); A a; } we issue: q.C: In function ‘void fn()’: q.C:8:4: error: expected ‘;’ before ‘a’ 8 | A a; | ^~ | ; Eh, what? clang++: q.C:8:3: error: must use 'struct' tag to refer to type 'A' in this scope A a; ^ struct q.C:7:5: note: struct 'A' is hidden by a non-type declaration of 'A' here B(A()); // extern struct B A (void); ^
next reply other threads:[~2020-10-22 15:27 UTC|newest] Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top 2020-10-22 15:27 mpolacek at gcc dot gnu.org [this message] 2020-10-25 22:32 ` [Bug c++/97531] " mpolacek at gcc dot gnu.org
Reply instructions: You may reply publicly to this message via plain-text email using any one of the following methods: * Save the following mbox file, import it into your mail client, and reply-to-all from there: mbox Avoid top-posting and favor interleaved quoting: https://en.wikipedia.org/wiki/Posting_style#Interleaved_style * Reply using the --to, --cc, and --in-reply-to switches of git-send-email(1): git send-email \ --in-reply-to=bug-97531-4@http.gcc.gnu.org/bugzilla/ \ --to=gcc-bugzilla@gcc.gnu.org \ --cc=gcc-bugs@gcc.gnu.org \ /path/to/YOUR_REPLY https://kernel.org/pub/software/scm/git/docs/git-send-email.html * If your mail client supports setting the In-Reply-To header via mailto: links, try the mailto: linkBe sure your reply has a Subject: header at the top and a blank line before the message body.
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).