[Bug libstdc++/109947] std::expected monadic operations do not support move-only error types yet

2023-06-06 Thread redi at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109947 Jonathan Wakely changed: What|Removed |Added Resolution|--- |FIXED Status|ASSIGNED

[Bug libstdc++/109947] std::expected monadic operations do not support move-only error types yet

2023-06-06 Thread aemseemann at gmail dot com via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109947 --- Comment #9 from Martin Seemann --- That's great news, looking forward to the next point release. Thank you very much for taking this to the committee and getting the process in motion so quickly!

[Bug libstdc++/109947] std::expected monadic operations do not support move-only error types yet

2023-06-01 Thread redi at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109947 Jonathan Wakely changed: What|Removed |Added Status|SUSPENDED |ASSIGNED

[Bug libstdc++/109947] std::expected monadic operations do not support move-only error types yet

2023-05-25 Thread redi at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109947 Jonathan Wakely changed: What|Removed |Added Status|RESOLVED|SUSPENDED Resolution|INVALID

[Bug libstdc++/109947] std::expected monadic operations do not support move-only error types yet

2023-05-25 Thread redi at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109947 --- Comment #6 from Jonathan Wakely --- (In reply to Martin Seemann from comment #5) > Thanks for the clarification! Now I am convinced that it is not a bug in > libstdc++ (although I still doubt that the side-effects were intended when > the

[Bug libstdc++/109947] std::expected monadic operations do not support move-only error types yet

2023-05-24 Thread aemseemann at gmail dot com via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109947 Martin Seemann changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution|---

[Bug libstdc++/109947] std::expected monadic operations do not support move-only error types yet

2023-05-24 Thread redi at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109947 --- Comment #4 from Jonathan Wakely --- (In reply to Martin Seemann from comment #3) > So it comes down to how to interpret the "Effects:" clause: Does "Equivalent > to " mean that all restrictions of > `value()` apply transitively or is it

[Bug libstdc++/109947] std::expected monadic operations do not support move-only error types yet

2023-05-24 Thread aemseemann at gmail dot com via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109947 --- Comment #3 from Martin Seemann --- Thanks for pointing me to the LWG issue. It makes sense that the error type must be copyable for the `value()` overloads due to potentially throwing a `bad_expected_access` with the embedded error

[Bug libstdc++/109947] std::expected monadic operations do not support move-only error types yet

2023-05-23 Thread redi at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109947 --- Comment #2 from Jonathan Wakely --- To be clear, a move-only value type is OK. A move-only error type is not.

[Bug libstdc++/109947] std::expected monadic operations do not support move-only error types yet

2023-05-23 Thread redi at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109947 --- Comment #1 from Jonathan Wakely --- (In reply to Martin Seemann from comment #0) > GCC13 introduce monadic operations for `std::expected`, including r-value > ref-qualified overloads, which suggests that it should be possible to use an >