public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "jg at jguk dot org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c++/109356] Enhancement idea to provide clearer missing brace line number Date: Tue, 04 Apr 2023 20:31:29 +0000 [thread overview] Message-ID: <bug-109356-4-vTNbcPr2r6@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-109356-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109356 --- Comment #3 from Jonny Grant <jg at jguk dot org> --- A different example where GCC does a good job of indicating the line number of a missing comma problem. https://godbolt.org/z/asGhE3W17 <source>:6:5: error: expected '}' before '{' token 6 | {"G", "H"}, | ^ <source>:2:1: note: to match this '{' 2 | { | ^ <source>:6:5: error: expected ',' or ';' before '{' token 6 | {"G", "H"}, | ^
next prev parent reply other threads:[~2023-04-04 20:31 UTC|newest] Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-03-31 10:00 [Bug c++/109356] New: " jg at jguk dot org 2023-03-31 10:17 ` [Bug c++/109356] " redi at gcc dot gnu.org 2023-03-31 10:50 ` xry111 at gcc dot gnu.org 2023-03-31 19:52 ` jg at jguk dot org 2023-04-04 20:31 ` jg at jguk dot org [this message] 2023-04-05 9:22 ` xry111 at gcc dot gnu.org 2023-04-06 22:19 ` jg at jguk dot org 2023-04-08 14:57 ` jg at jguk dot org 2023-04-09 9:04 ` xry111 at gcc dot gnu.org 2023-04-09 20:10 ` jg at jguk dot 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-109356-4-vTNbcPr2r6@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).