public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "cvs-commit at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libstdc++/95904] Improve the diagnostic for conflicting return types in std::visit
Date: Fri, 09 Oct 2020 17:49:12 +0000 [thread overview]
Message-ID: <bug-95904-4-vSL6l8tYvE@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-95904-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=95904
--- Comment #1 from CVS Commits <cvs-commit at gcc dot gnu.org> ---
The master branch has been updated by Ville Voutilainen <ville@gcc.gnu.org>:
https://gcc.gnu.org/g:3427e31331677ca826c5588c87924214f7e5c54b
commit r11-3760-g3427e31331677ca826c5588c87924214f7e5c54b
Author: Ville Voutilainen <ville.voutilainen@gmail.com>
Date: Fri Oct 9 20:47:01 2020 +0300
libstdc++: Diagnose visitors with different return types [PR95904]
libstdc++-v3/ChangeLog:
PR libstdc++/95904
* include/std/variant (__deduce_visit_result): Add a nested ::type.
(__gen_vtable_impl</*base case*/>::_S_apply):
Check the visitor return type.
(__same_types): New.
(__check_visitor_result): Likewise.
(__check_visitor_results): Likewise.
(visit(_Visitor&&, _Variants&&...)): Use __check_visitor_results
in case we're visiting just one variant.
* testsuite/20_util/variant/visit_neg.cc: Adjust.
next prev parent reply other threads:[~2020-10-09 17:49 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-25 23:40 [Bug libstdc++/95904] New: " rs2740 at gmail dot com
2020-06-26 0:26 ` [Bug libstdc++/95904] " redi at gcc dot gnu.org
2020-06-29 11:13 ` ville.voutilainen at gmail dot com
2020-10-09 17:49 ` cvs-commit at gcc dot gnu.org [this message]
2020-10-09 17:50 ` ville.voutilainen at gmail dot com
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-95904-4-vSL6l8tYvE@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: link
Be 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).