public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "redi at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libstdc++/109947] std::expected monadic operations do not support move-only error types yet
Date: Thu, 01 Jun 2023 22:54:13 +0000 [thread overview]
Message-ID: <bug-109947-4-gYImQ43hAl@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-109947-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109947
Jonathan Wakely <redi at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|SUSPENDED |ASSIGNED
Assignee|unassigned at gcc dot gnu.org |redi at gcc dot gnu.org
Target Milestone|--- |13.2
--- Comment #8 from Jonathan Wakely <redi at gcc dot gnu.org> ---
The LWG issue has been moved to Tentatively Ready status by LWG, and should get
approved by the full committee in two weeks.
I've implemented the proposed resolution in GCC trunk as
r14-1471-gfe94f8b7e022b7 and will backport that to the gcc-13 branch too.
next prev parent reply other threads:[~2023-06-01 22:54 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-23 19:12 [Bug libstdc++/109947] New: " aemseemann at gmail dot com
2023-05-23 23:32 ` [Bug libstdc++/109947] " redi at gcc dot gnu.org
2023-05-23 23:36 ` redi at gcc dot gnu.org
2023-05-24 19:34 ` aemseemann at gmail dot com
2023-05-24 20:25 ` redi at gcc dot gnu.org
2023-05-24 21:16 ` aemseemann at gmail dot com
2023-05-25 8:06 ` redi at gcc dot gnu.org
2023-05-25 16:03 ` redi at gcc dot gnu.org
2023-06-01 22:54 ` redi at gcc dot gnu.org [this message]
2023-06-06 19:11 ` aemseemann at gmail dot com
2023-06-06 22:59 ` 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-109947-4-gYImQ43hAl@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).