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++/107430] New: [meta-bug] lambda in decltype Date: Thu, 27 Oct 2022 05:10:56 +0000 [thread overview] Message-ID: <bug-107430-4@http.gcc.gnu.org/bugzilla/> (raw) https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107430 Bug ID: 107430 Summary: [meta-bug] lambda in decltype Product: gcc Version: 12.0 Status: UNCONFIRMED Keywords: c++-lambda, meta-bug, rejects-valid Severity: normal Priority: P3 Component: c++ Assignee: unassigned at gcc dot gnu.org Reporter: pinskia at gcc dot gnu.org Target Milestone: --- I noticed there are many issues with lambda inside a decltype issues. Especially dealing with template alias.
next reply other threads:[~2022-10-27 5:10 UTC|newest] Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-10-27 5:10 pinskia at gcc dot gnu.org [this message] 2023-07-11 13:42 ` [Bug c++/107430] " ppalka at gcc dot gnu.org 2024-02-29 16:02 ` mpolacek at gcc dot gnu.org 2024-04-12 19:21 ` ppalka at gcc dot gnu.org 2024-04-13 7:33 ` pinskia at gcc dot gnu.org 2024-04-13 7:34 ` pinskia at gcc dot gnu.org 2024-04-13 7:35 ` pinskia at gcc dot gnu.org 2024-04-13 7:47 ` pinskia at gcc dot gnu.org 2024-04-13 7:49 ` pinskia at gcc dot gnu.org 2024-04-13 7:50 ` pinskia at gcc dot gnu.org 2024-04-13 7:51 ` pinskia at gcc dot gnu.org 2024-04-13 7:54 ` pinskia at gcc dot gnu.org 2024-04-13 7:57 ` pinskia at gcc dot gnu.org 2024-04-13 7:58 ` pinskia at gcc dot gnu.org 2024-04-13 8:00 ` pinskia at gcc dot gnu.org 2024-04-13 8:03 ` pinskia at gcc dot gnu.org 2024-04-13 8:05 ` pinskia at gcc dot gnu.org 2024-04-13 8:06 ` pinskia at gcc dot gnu.org 2024-04-13 8:06 ` pinskia at gcc dot gnu.org 2024-04-13 8:07 ` pinskia at gcc dot gnu.org 2024-04-13 8:11 ` pinskia at gcc dot gnu.org 2024-04-13 8:13 ` pinskia at gcc dot gnu.org 2024-04-13 8:15 ` pinskia at gcc dot gnu.org 2024-04-13 8:17 ` pinskia at gcc dot gnu.org 2024-04-13 8:18 ` pinskia at gcc dot gnu.org 2024-04-13 8:21 ` pinskia at gcc dot gnu.org 2024-04-13 8:25 ` pinskia at gcc dot gnu.org 2024-04-13 8:27 ` pinskia at gcc dot gnu.org 2024-04-13 8:28 ` pinskia at gcc dot gnu.org 2024-04-13 8:29 ` pinskia at gcc dot gnu.org 2024-04-13 8:31 ` pinskia at gcc dot gnu.org 2024-04-13 8:36 ` pinskia at gcc dot gnu.org 2024-04-13 15:13 ` ppalka at gcc dot gnu.org 2024-04-13 15:14 ` ppalka at gcc dot gnu.org 2024-04-13 15:15 ` ppalka at gcc dot gnu.org 2024-04-13 20:18 ` pinskia at gcc dot gnu.org 2024-04-13 20:44 ` 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-107430-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).