From: Jonathan Wakely <jwakely@redhat.com>
To: libstdc++@gcc.gnu.org, gcc-patches@gcc.gnu.org
Subject: [committed] libstdc++: Remove template-head from std::expected<void> ctor [PR109182]
Date: Mon, 20 Mar 2023 09:36:29 +0000 [thread overview]
Message-ID: <20230320093629.15801-1-jwakely@redhat.com> (raw)
Tested x86_64-linux. Pushed to trunk. Will backport to gcc-12 too.
-- >8 --
The presence of a template-head on this constructor is a copy & paste
error from the primary template.
libstdc++-v3/ChangeLog:
PR libstdc++/109182
* include/std/expected (expected<void>::expected(in_place_t)):
Remove template-head.
---
libstdc++-v3/include/std/expected | 9 ++++-----
1 file changed, 4 insertions(+), 5 deletions(-)
diff --git a/libstdc++-v3/include/std/expected b/libstdc++-v3/include/std/expected
index 9a52e2574bf..567a5195e8d 100644
--- a/libstdc++-v3/include/std/expected
+++ b/libstdc++-v3/include/std/expected
@@ -1302,11 +1302,10 @@ namespace __expected
: _M_unex(std::move(__u).error()), _M_has_value(false)
{ }
- template<typename... _Args>
- constexpr explicit
- expected(in_place_t) noexcept
- : expected()
- { }
+ constexpr explicit
+ expected(in_place_t) noexcept
+ : expected()
+ { }
template<typename... _Args>
requires is_constructible_v<_Er, _Args...>
--
2.39.2
reply other threads:[~2023-03-20 9:36 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20230320093629.15801-1-jwakely@redhat.com \
--to=jwakely@redhat.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=libstdc++@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).