[Bug libstdc++/105118] New: Why is unexpected::value() named error() in libstdc++?

[Bug libstdc++/105118] New: Why is unexpected::value() named error() in libstdc++?

[hewillk at gmail dot com]

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?

[Bug libstdc++/105118] Why is unexpected::value() named error() in libstdc++?

[de34 at live dot cn]

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.

[Bug libstdc++/105118] Why is unexpected::value() named error() in libstdc++?

[redi at gcc dot gnu.org]

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.

[Bug libstdc++/105118] Why is unexpected::value() named error() in libstdc++?

[hewillk at gmail dot com]

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.