public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "pinskia at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c/103996] Enhancement: Better diagnostic for invalid reuse of a function name Date: Wed, 12 Jan 2022 18:15:40 +0000 [thread overview] Message-ID: <bug-103996-4-yymCxaj44B@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-103996-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103996 --- Comment #1 from Andrew Pinski <pinskia at gcc dot gnu.org> --- C++ front-end produces: <source>: In function 'void f()': <source>:4:10: error: invalid types '<unresolved overloaded function type>[int]' for array subscript 4 | index[0] = 0; | ^ Which seems better.
next prev parent reply other threads:[~2022-01-12 18:15 UTC|newest] Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-01-12 18:13 [Bug c/103996] New: " nightstrike at gmail dot com 2022-01-12 18:15 ` pinskia at gcc dot gnu.org [this message] 2022-01-12 18:23 ` [Bug c/103996] " pinskia at gcc dot gnu.org 2022-01-12 18:38 ` [Bug c/103996] Provide " pinskia at gcc dot gnu.org 2022-01-13 11:40 ` egallager 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-103996-4-yymCxaj44B@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).