public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
* [Bug libstdc++/105118] New: Why is unexpected::value() named error() in libstdc++?
@ 2022-03-31 17:51 hewillk at gmail dot com
2022-04-01 7:33 ` [Bug libstdc++/105118] " de34 at live dot cn
` (2 more replies)
0 siblings, 3 replies; 4+ messages in thread
From: hewillk at gmail dot com @ 2022-03-31 17:51 UTC (permalink / raw)
To: gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105118
Bug ID: 105118
Summary: Why is unexpected::value() named error() in libstdc++?
Product: gcc
Version: 12.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: libstdc++
Assignee: unassigned at gcc dot gnu.org
Reporter: hewillk at gmail dot com
Target Milestone: ---
In libstdc++'s implementation of std::expected, std::unexpected gets the _M_val
through error(), but in [expected.un.object.general], unexpected uses value()
to access val.
In my opinion, error() should be a better member function name, but the
standard currently uses value(). So I wonder why libstdc++ uses error()? Is
there any information about this?
^ permalink raw reply [flat|nested] 4+ messages in thread* [Bug libstdc++/105118] Why is unexpected::value() named error() in libstdc++? 2022-03-31 17:51 [Bug libstdc++/105118] New: Why is unexpected::value() named error() in libstdc++? hewillk at gmail dot com @ 2022-04-01 7:33 ` de34 at live dot cn 2022-04-01 11:37 ` redi at gcc dot gnu.org 2023-12-01 5:07 ` hewillk at gmail dot com 2 siblings, 0 replies; 4+ messages in thread From: de34 at live dot cn @ 2022-04-01 7:33 UTC (permalink / raw) To: gcc-bugs https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105118 Jiang An <de34 at live dot cn> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |de34 at live dot cn --- Comment #1 from Jiang An <de34 at live dot cn> --- I think currently libstdc++ also implements P2549R0 (https://wg21.link/p2549r0). Let's suspend the issue until whether P2549R0 is accepted or rejected is determined. ^ permalink raw reply [flat|nested] 4+ messages in thread
* [Bug libstdc++/105118] Why is unexpected::value() named error() in libstdc++? 2022-03-31 17:51 [Bug libstdc++/105118] New: Why is unexpected::value() named error() in libstdc++? hewillk at gmail dot com 2022-04-01 7:33 ` [Bug libstdc++/105118] " de34 at live dot cn @ 2022-04-01 11:37 ` redi at gcc dot gnu.org 2023-12-01 5:07 ` hewillk at gmail dot com 2 siblings, 0 replies; 4+ messages in thread From: redi at gcc dot gnu.org @ 2022-04-01 11:37 UTC (permalink / raw) To: gcc-bugs https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105118 Jonathan Wakely <redi at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Ever confirmed|0 |1 Last reconfirmed| |2022-04-01 Status|UNCONFIRMED |SUSPENDED --- Comment #2 from Jonathan Wakely <redi at gcc dot gnu.org> --- (In reply to Jiang An from comment #1) > I think currently libstdc++ also implements P2549R0 Correct. It's already been approved by LEWG and I see no reason to think it won't be approved by the full committee. ^ permalink raw reply [flat|nested] 4+ messages in thread
* [Bug libstdc++/105118] Why is unexpected::value() named error() in libstdc++? 2022-03-31 17:51 [Bug libstdc++/105118] New: Why is unexpected::value() named error() in libstdc++? hewillk at gmail dot com 2022-04-01 7:33 ` [Bug libstdc++/105118] " de34 at live dot cn 2022-04-01 11:37 ` redi at gcc dot gnu.org @ 2023-12-01 5:07 ` hewillk at gmail dot com 2 siblings, 0 replies; 4+ messages in thread From: hewillk at gmail dot com @ 2023-12-01 5:07 UTC (permalink / raw) To: gcc-bugs https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105118 康桓瑋 <hewillk at gmail dot com> changed: What |Removed |Added ---------------------------------------------------------------------------- Resolution|--- |INVALID Status|SUSPENDED |RESOLVED --- Comment #3 from 康桓瑋 <hewillk at gmail dot com> --- Closed as P2549 was approved in C++23. ^ permalink raw reply [flat|nested] 4+ messages in thread
end of thread, other threads:[~2023-12-01 5:07 UTC | newest] Thread overview: 4+ messages (download: mbox.gz / follow: Atom feed) -- links below jump to the message on this page -- 2022-03-31 17:51 [Bug libstdc++/105118] New: Why is unexpected::value() named error() in libstdc++? hewillk at gmail dot com 2022-04-01 7:33 ` [Bug libstdc++/105118] " de34 at live dot cn 2022-04-01 11:37 ` redi at gcc dot gnu.org 2023-12-01 5:07 ` hewillk at gmail dot com
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).