[Development] RFC: Containers member functions for algorithm

Ville Voutilainen ville.voutilainen at gmail.com
Thu Mar 23 11:01:12 CET 2017


On 23 March 2017 at 11:36, Marc Mutz <marc.mutz at kdab.com> wrote:
> That said, there's a reason why there's no std::sort(Container &). It's
> because you need Concepts to disambiguate the various overloads. Well, that
> and because Eric Niebler doesn't manage to limit the scope of his range
> proposals.

The TS proposal is quite tightly scoped. It doesn't have range views
and range actions, for
instance.

> matters whether a function is a member or a free function. There're proposals
> floating around for years to make o.f() fall back to f(o) for std C++. Ville
> can probably say more about the status of these. This is a problem that can be

That proposal was rejected, whether it will come back in some form is
for the moment unknown.



More information about the Development mailing list