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 r10-9561] libstdc++: Simplify constraints for semiregular-box [LWG 3477] Date: Mon, 29 Mar 2021 20:00:36 +0000 (GMT) [thread overview] Message-ID: <20210329200036.5F5FC3851C3E@sourceware.org> (raw) https://gcc.gnu.org/g:1649b523067f2bd8e5c872db36c8cf00c99f8832 commit r10-9561-g1649b523067f2bd8e5c872db36c8cf00c99f8832 Author: Jonathan Wakely <jwakely@redhat.com> Date: Mon Sep 7 20:09:17 2020 +0100 libstdc++: Simplify constraints for semiregular-box [LWG 3477] libstdc++-v3/ChangeLog: * include/std/ranges (__box): Simplify constraints as per LWG 3477. (cherry picked from commit 00ffe730072f5e2e1923692163dc37db7b3784cb) Diff: --- libstdc++-v3/include/std/ranges | 6 ++++-- 1 file changed, 4 insertions(+), 2 deletions(-) diff --git a/libstdc++-v3/include/std/ranges b/libstdc++-v3/include/std/ranges index a93a698c40a..4b596d41a47 100644 --- a/libstdc++-v3/include/std/ranges +++ b/libstdc++-v3/include/std/ranges @@ -494,10 +494,12 @@ namespace ranges using std::optional<_Tp>::operator=; + // _GLIBCXX_RESOLVE_LIB_DEFECTS + // 3477. Simplify constraints for semiregular-box __box& operator=(const __box& __that) noexcept(is_nothrow_copy_constructible_v<_Tp>) - requires (!assignable_from<_Tp&, const _Tp&>) + requires (!copyable<_Tp>) { if ((bool)__that) this->emplace(*__that); @@ -509,7 +511,7 @@ namespace ranges __box& operator=(__box&& __that) noexcept(is_nothrow_move_constructible_v<_Tp>) - requires (!assignable_from<_Tp&, _Tp>) + requires (!movable<_Tp>) { if ((bool)__that) this->emplace(std::move(*__that));
reply other threads:[~2021-03-29 20:00 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=20210329200036.5F5FC3851C3E@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: 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).