On 06/03/2025 20.12, Arthur O'Dwyer via Std-Proposals wrote:
> On Thu, Mar 6, 2025 at 1:50 PM Jens Maurer via Std-Proposals <std-proposals_at_[hidden] <mailto:std-proposals_at_[hidden]>> wrote:

> We should have this ASAP, with a modern implementation. Any takers?
>
>
> I'd happily review new wording/implementation, but am not inclined to author.
>
> IIUC, the design intent is that this doesn't change any /existing/ behavior or signatures of min/max/minmax, but merely expands the range of well-formed calls to include a lot of things that are ill-formed today?
> auto x = std::minmax(A(), A()); // same old behavior
> auto y = std::minmax(A(), B()); // today: ill-formed; tomorrow: shiny new behavior
> right?

I wouldn't be opposed to detecting xvalue arguments and returning
something other than a (soon-to-be-dangling) lvalue in that case.
Maybe there's something to learn from the borrowed_range machinery.

Jens