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++/107858] structed binding with auto type and for all loop in a template considered a type dependent name Date: Thu, 24 Nov 2022 15:13:12 +0000 [thread overview] Message-ID: <bug-107858-4-vY4eNpMR2L@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-107858-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107858 Andrew Pinski <pinskia at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|UNCONFIRMED |NEW Ever confirmed|0 |1 Summary|Variable in generic lambda |structed binding with auto |incorrectly considered to |type and for all loop in a |be a dependent name |template considered a type | |dependent name Last reconfirmed| |2022-11-24 --- Comment #1 from Andrew Pinski <pinskia at gcc dot gnu.org> --- This is unrelated to generic lambdas and can reproduce with just a templated function: ``` struct y { template<int> void foo() const {} }; template<typename T> struct pair { T a, b; }; template<class t> void bar(void) { pair<y> x[10]; for (auto const &[a, b] : x) a.foo<0>(); } ``` Note the forall loop is required. I wonder if that is because begin and end are considered type depdent ... But not using structured binding, GCC does not considered them as type depdent. Confirmed.
next prev parent reply other threads:[~2022-11-24 15:13 UTC|newest] Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-11-24 12:44 [Bug c++/107858] New: Variable in generic lambda incorrectly considered to be a " pilarlatiesa at gmail dot com 2022-11-24 15:13 ` pinskia at gcc dot gnu.org [this message] 2022-11-24 15:14 ` [Bug c++/107858] structured binding with auto type and for all loop in a template considered a type " pinskia 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-107858-4-vY4eNpMR2L@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).