public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "ppalka at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c++/99678] [concepts] requires-clause allows undeclared identifier Date: Thu, 13 Jun 2024 14:18:48 +0000 [thread overview] Message-ID: <bug-99678-4-A6KCxMCBmH@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-99678-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99678 Patrick Palka <ppalka at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Target Milestone|--- |14.2
next prev parent reply other threads:[~2024-06-13 14:18 UTC|newest] Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-03-20 4:17 [Bug c++/99678] New: c++20 trailing requires clauses " hewillk at gmail dot com 2024-05-07 14:12 ` [Bug c++/99678] " ppalka at gcc dot gnu.org 2024-05-07 14:13 ` [Bug c++/99678] [concepts] requires-clause " ppalka at gcc dot gnu.org 2024-06-12 18:25 ` ppalka at gcc dot gnu.org 2024-06-12 18:25 ` ppalka at gcc dot gnu.org 2024-06-13 14:16 ` cvs-commit at gcc dot gnu.org 2024-06-13 14:18 ` ppalka at gcc dot gnu.org [this message] 2024-06-17 14:26 ` cvs-commit at gcc dot gnu.org 2024-06-17 14:27 ` ppalka 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-99678-4-A6KCxMCBmH@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).