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++/103013] Underconstrained constructor span(_Range&&)
Date: Mon, 01 Nov 2021 23:51:14 +0000 [thread overview]
Message-ID: <bug-103013-4-ROQHkJg2p8@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-103013-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103013
--- Comment #7 from CVS Commits <cvs-commit at gcc dot gnu.org> ---
The master branch has been updated by Jonathan Wakely <redi@gcc.gnu.org>:
https://gcc.gnu.org/g:09bc98098e4ad474d2ba9da52457b29bbd08874b
commit r12-4833-g09bc98098e4ad474d2ba9da52457b29bbd08874b
Author: Jonathan Wakely <jwakely@redhat.com>
Date: Mon Nov 1 11:32:39 2021 +0000
libstdc++: Reorder constraints on std::span::span(Range&&) constructor.
In PR libstdc++/103013 Tim Song pointed out that we could reorder the
constraints of this constructor. That's worth doing just to reduce the
work the compiler has to do during overload resolution, even if it isn't
needed to make the code in the PR work.
libstdc++-v3/ChangeLog:
* include/std/span (span(Range&&)): Reorder constraints.
next prev parent reply other threads:[~2021-11-01 23:51 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-31 9:48 [Bug libstdc++/103013] New: " andrey.davydov at jetbrains dot com
2021-10-31 9:50 ` [Bug libstdc++/103013] " andrey.davydov at jetbrains dot com
2021-10-31 18:11 ` redi at gcc dot gnu.org
2021-10-31 18:13 ` redi at gcc dot gnu.org
2021-11-01 3:12 ` rs2740 at gmail dot com
2021-11-01 5:23 ` andrey.davydov at jetbrains dot com
2021-11-01 11:32 ` redi at gcc dot gnu.org
2021-11-01 23:51 ` cvs-commit at gcc dot gnu.org [this message]
2021-11-01 23:54 ` redi at gcc dot gnu.org
2022-04-21 12:33 ` cvs-commit at gcc dot gnu.org
2022-04-26 13:13 ` cvs-commit at gcc dot gnu.org
2022-04-26 13:21 ` 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-103013-4-ROQHkJg2p8@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).