|
|
|
|
|
|
by jng
1031 days 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. |
|
|
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?