Why does shared_ptr signature differ from unique_ptr for arrays?

Question

std::unique_ptr<int[]> p(new int[10]); //ok

std::shared_ptr<int[]> p(new int[10]); //Error

shared_ptr<int> sp( new int[10],[](int *p){delete [] p;});
                                       //Ok, writing custom deleter for
                                       //array since shared_ptr will call
                                       //delete by default.

Is there any specific reason shared_ptr signature is different for arrays when compared to unique_ptr?

It would have been simpler if both api followed similar signature.

Another difference is that there is no `weak_ptr<>` for `unique_ptr<>`. — jxh, Oct 06 '13 at 09:44
unique_ptr has a template specialization to allow the array while shared_ptr does not. — billz, Oct 06 '13 at 09:47
dup? http://stackoverflow.com/questions/16711697/is-there-any-use-for-unique-ptr-with-array — billz, Oct 06 '13 at 09:52

score 6 · Accepted Answer · edited May 23 '17 at 12:24

6

unique_ptr has an explicit template specialization to handle array objects. The LWG (Library Working Group of the C++ committee) briefly considered the possibility of shared_ptr<T[]> but apparently it wasn't of sufficiently high priority to make it into the standard, there was also some controversy over the consequences of the arithmetic on shared_ptr<T[]>

edited May 23 '17 at 12:24

Community

1
1

answered Oct 06 '13 at 10:09

Gearoid Murphy

11,834
17
68
86

Why does shared_ptr signature differ from unique_ptr for arrays?

1 Answers1