public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "hewillk at gmail dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug libstdc++/106589] New: visit<void> rejects lambdas that do not return void Date: Fri, 12 Aug 2022 03:27:42 +0000 [thread overview] Message-ID: <bug-106589-4@http.gcc.gnu.org/bugzilla/> (raw) https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106589 Bug ID: 106589 Summary: visit<void> rejects lambdas that do not return void Product: gcc Version: 13.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: libstdc++ Assignee: unassigned at gcc dot gnu.org Reporter: hewillk at gmail dot com Target Milestone: --- #include <variant> int main() { std::visit<void>([]{ return 0; }); } https://godbolt.org/z/G3Penchbx
next reply other threads:[~2022-08-12 3:27 UTC|newest] Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-08-12 3:27 hewillk at gmail dot com [this message] 2022-08-12 3:34 ` [Bug libstdc++/106589] " hewillk at gmail dot com 2022-08-12 6:04 ` [Bug libstdc++/106589] [12/13 Regression] " pinskia at gcc dot gnu.org 2022-08-12 6:09 ` pinskia at gcc dot gnu.org 2022-08-12 22:00 ` redi at gcc dot gnu.org 2022-08-24 13:01 ` [Bug libstdc++/106589] [12 " cvs-commit at gcc dot gnu.org 2022-08-24 13:02 ` 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-106589-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).