Why don’t std::vector’s elements need a default constructor?

by

std::vector doesn’t need the default constructor because it never uses it. Every time it needs to construct an element, it does it by using the copy constructor, because every time it has something to copy: either existing vector element or an element you yourself supplied for copying through a method’s parameter (explicitly or implicitly, by relying on a default argument)

You can write a class like that in exactly the same way: every time you need to construct a new element in your array, require the user to supply an element for copying. In this case constructing that original element becomes user’s responsibility.

Every time it appears as if std::vector “requires” a default constructor from you, it simply means that somewhere you relied on a default argument of some of the vectors methods, i.e. it was you who tried to default-construct an element, not the vector. The vector itself, again, will never try to default-construct elements.

In order to avoid the default constructor requirement during memory allocation, standard library allocates raw uninitialized memory block and then immediately copy-constructs new elements in that raw memory block (which is something new[] cannot do). This functionality is incapsulated in std::allocator class. You can use std::allocator in your code as well, meaning that the “magic” is immediately available to you too.

Note: The above applies to pre-C++11 version of C++ language specification. C++11 changed a lot of things. And these changes do create situations in which std::vector can use default constructors internally.

Also it might be worth noting that even the original C++98 specification allowed implementations to use function overloading instead of default arguments in order to implement the standard library interface. This means that formally it is possible to have a valid C++98 implementation of std::vector that uses default constructors internally.

More Related Contents:

  1. C++ : Unable to read from large txt file [closed]
  2. Invalid operands to binary expression while implementing vector [closed]
  3. Difficulties on atributting a array to another [closed]
  4. Erasing elements from a vector
  5. Why can’t I make a vector of references?
  6. Choice between vector::resize() and vector::reserve()
  7. Using arrays or std::vectors in C++, what’s the performance gap?
  8. Does C++11 allow vector?
  9. When vectors are allocated, do they use memory on the heap or the stack?
  10. How can I create cartesian product of vector of vectors?
  11. vector size – 1 when size is 0 in C++
  12. When is a private constructor not a private constructor?
  13. Erasing from a std::vector while doing a for each?
  14. How to read a binary file into a vector of unsigned chars
  15. How to use std::sort with a vector of structures and compare function?
  16. How to navigate through a vector using iterators? (C++)
  17. Compute Median of Values Stored In Vector – C++?
  18. Initial capacity of vector in C++
  19. std::vector iterator invalidation
  20. Compile time triggered range check for std::vector
  21. Does resizing a vector invalidate iterators?
  22. size vs capacity of a vector?
  23. Why doesn’t emplace_back() use uniform initialization?
  24. Erase element in vector while iterating the same vector [duplicate]
  25. How do I pass multiple ints into a vector at once?
  26. Can std::vector emplace_back copy construct from an element of the vector itself?
  27. Benefits of using reserve() in a vector – C++
  28. iterator for 2d vector
  29. Initializing an std::array of non-default-constructible elements?
  30. Checking if all elements of a vector are equal in C++

Leave a Comment