4 ms·

I have written and been using that same smart pointer type for years, under the pretty horrible name of holder_cloner_t<> (at least it's clear). It is indeed th

by jng 3y ago

I have written and been using that same smart pointer type for years, under the pretty horrible name of holder_cloner_t<> (at least it's clear). It is indeed the right solution to a very common and important type of problem. Looking forward to something like this in the standard library one of these decades.

zabzonk 3y ago
> It is indeed the right solution to a very common and important type of problem if it is such a solution to such a common problem (both of which i dispute), why do you think it is not alredy in the standard library?