public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c++/113798] [C++26] P2662R3 - Pack indexing Date: Thu, 09 May 2024 13:20:09 +0000 [thread overview] Message-ID: <bug-113798-4-kHltRV6ejQ@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-113798-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113798 --- Comment #1 from Jakub Jelinek <jakub at gcc dot gnu.org> --- Note, I wonder if the paper didn't go too far with the noptr-abstract-pack-declarator [ constant-expression[opt] ] attribute-specifier-seq[opt] production removal. It removes the unwanted T...[4] case which ought to be parsed as pack indexing, sure, but doesn't it also unnecessarily make <template ...T> void foo (T...(int)[10]) { } invalid as well?
next prev parent reply other threads:[~2024-05-09 13:20 UTC|newest] Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top 2024-02-07 9:45 [Bug c++/113798] New: " jakub at gcc dot gnu.org 2024-02-07 13:48 ` [Bug c++/113798] " mpolacek at gcc dot gnu.org 2024-05-09 13:20 ` jakub at gcc dot gnu.org [this message] 2024-05-09 19:06 ` jakub 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-113798-4-kHltRV6ejQ@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).