Mailing list review (June 3 - June 16 2024)

• Brian started work on a new revision https://isocpp.org/files/papers/D3182R1.html
• Jonathan started work on a similar design a while back https://kayari.org/cxx/stack_pop.html - I would invite the authors to join forces.
• We think only supporting container adapters is arbitrary and want to see the design extended to all sequence containers that have pop* methods.
  In its current form, it's unclear to me whether we have a strong consensus to spend time on this.
• Multiple people have expressed that using move_if_noexcept would increase consensus and make inclusion in the standard more motivated
• However, using move_if_noexcept has its own set of pitfalls. I don't think we are going to resolve that on the mailing list. We need to poll that specific point when presented in a meeting/telecon
• There is the idea of a user-specialized type trait to indicate whether a move constructor is exception safe, that might be worth exploring.
• A third option is to only provide the methods on containers with exception-safe elements

Consequently, we will probably schedule this paper for a telecon once the new draft is published

P3182R1 Add container pop methods that return the popped value (Brian Bi, Add container pop methods that return the popped value)

Is this paper still in the queue to be scheduled for a telecon?