public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "redi at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug libstdc++/105291] include/c++/12.0.1/debug/safe_unordered_container.h:71:28: error: captured variable '__local_end' cannot appear here Date: Sat, 16 Apr 2022 14:18:05 +0000 [thread overview] Message-ID: <bug-105291-4-Y91W4RRFDQ@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-105291-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105291 --- Comment #3 from Jonathan Wakely <redi at gcc dot gnu.org> --- https://github.com/cplusplus/CWG/issues/31
next prev parent reply other threads:[~2022-04-16 14:18 UTC|newest] Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-04-16 8:51 [Bug libstdc++/105291] New: " sbergman at redhat dot com 2022-04-16 13:35 ` [Bug libstdc++/105291] " redi at gcc dot gnu.org 2022-04-16 13:39 ` redi at gcc dot gnu.org 2022-04-16 14:18 ` redi at gcc dot gnu.org [this message] 2022-04-17 14:36 ` corentinjabot at gmail dot com 2022-04-19 12:11 ` sbergman at redhat dot com 2022-04-19 12:15 ` redi 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-105291-4-Y91W4RRFDQ@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).