Why C++ containers don’t allow incomplete types?

by

Matt Austern, the chair of the C++ standardization committee’s library working group, explained this decision of the committee in his Dr. Dobb’s article by historical reasons:

We discovered, with more testing, that even the [simple] example didn’t work with every STL implementation. In the end, it all seemed too murky and too poorly understood; the standardization committee didn’t think there was any choice except to say that STL containers aren’t supposed to work with incomplete types. For good measure, we applied that prohibition to the rest of the standard library too.

My understanding of this is that the committee did not want to invalidate existing implementations of the library by requiring them to support incomplete types retroactively.

In the same article he concedes that

In a future revision of C++, it might make sense to relax the restriction on instantiating standard library templates with incomplete types.

Given that the article dates back to 2002, and the prohibition remains in place in the current standard, I think that the decision of the boost designers not to wait for the future and build their own containers that allow incomplete types was fully justified.

Edit: See this answer for information on using incomplete types allowed by C++17 standard for some containers in the Standard C++ Library.

More Related Contents:

  1. Can standard container templates be instantiated with incomplete types?
  2. Determine if a type is an STL container at compile time
  3. How can I declare a member vector of the same class?
  4. Template class with template container
  5. Standard Library Containers with additional optional template parameters?
  6. C++ std::map holding ANY type of value
  7. Why is the STL so heavily based on templates instead of inheritance?
  8. Incomplete class usage in template
  9. C++ template function compiles in header but not implementation
  10. Obtain container type from (its) iterator type in C++ (STL)
  11. Why does stack not compile in g++? [duplicate]
  12. Where and why do I have to put the “template” and “typename” keywords?
  13. Erasing elements from a vector
  14. Why can’t I make a vector of references?
  15. Concise explanation of reference collapsing rules requested: (1) A& & -> A& , (2) A& && -> A& , (3) A&& & -> A& , and (4) A&& && -> A&&
  16. “Undefined reference to” template class constructor [duplicate]
  17. Metaprograming: Failure of Function Definition Defines a Separate Function
  18. Iteration over std::vector: unsigned vs signed index variable
  19. A better way to avoid public member invisibility and source code bloat/repetition with inherited class templates?
  20. Why is value taking setter member functions not recommended in Herb Sutter’s CppCon 2014 talk (Back to Basics: Modern C++ Style)?
  21. Non-copyable elements in vector
  22. How to make elements of vector unique? (remove non adjacent duplicates)
  23. Template typedefs – What’s your work around?
  24. STL deque accessing by index is O(1)?
  25. Deciphering C++ template error messages
  26. Incrementing iterators: Is ++it more efficient than it++? [duplicate]
  27. Implicit conversion when overloading operators for template classes
  28. Why is a C++ Vector called a Vector? [closed]
  29. Types of iterator : Output vs. Input vs. Forward vs. Random Access Iterator
  30. Why is partial specialization of a nested class template allowed, while complete isn’t?

Leave a Comment