public inbox for libstdc++-cvs@sourceware.org
help / color / mirror / Atom feed
From: Jonathan Wakely <redi@gcc.gnu.org>
To: gcc-cvs@gcc.gnu.org, libstdc++-cvs@gcc.gnu.org
Subject: [gcc r13-6759] libstdc++: Remove template-head from std::expected<void> ctor [PR109182]
Date: Mon, 20 Mar 2023 09:36:05 +0000 (GMT)	[thread overview]
Message-ID: <20230320093605.192BA3858D20@sourceware.org> (raw)

https://gcc.gnu.org/g:5194ad1958cbfe800357571fad68be8bc8b7d915

commit r13-6759-g5194ad1958cbfe800357571fad68be8bc8b7d915
Author: Jonathan Wakely <jwakely@redhat.com>
Date:   Mon Mar 20 09:30:58 2023 +0000

    libstdc++: Remove template-head from std::expected<void> ctor [PR109182]
    
    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.

Diff:
---
 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...>

                 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=20230320093605.192BA3858D20@sourceware.org \
    --to=redi@gcc.gnu.org \
    --cc=gcc-cvs@gcc.gnu.org \
    --cc=libstdc++-cvs@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).