C++ Handbook

Header Reference: <list>

Header Reference: <list>

Doubly-linked list container facilities from <list>.

How to use this reference page

Use reference pages to confirm names, categories, nearby facilities, and the constraints that matter before writing or reviewing code.

  • Scan the top of the page first to identify the primary types, functions, or algorithm families involved.
  • Use the nearby-page links when your question is really about a companion header, related algorithm family, or broader subsystem.
  • Validate tricky behavior with a small compileable example before relying on memory for details like invalidation, ordering, allocation, or lifetime rules.

What header pages are for

Header reference pages are meant to answer a practical question quickly: what this header provides, when to reach for it, and which usage rules are easiest to get wrong.

  • Start here when you already know roughly which header you need but want a fast operational summary.
  • Use the example section below as a minimal pattern, then adapt it to your real container, ownership, text, or concurrency workflow.
  • Jump to broader index pages when you need exhaustive coverage rather than a header-focused summary.

Header Reference: <list>

Main facilities

What this header is for

Use <list> when node stability and splicing behavior matter more than cache locality and contiguous traversal speed.

Common patterns

Notes

Minimal example

#include <list>

int main() {
    // Start with the primary facility from <list>.
    // Then verify lifetime, invalidation, ordering, or error-handling rules.
    return 0;
}

What to verify before relying on this header

  • Which operations invalidate iterators, references, pointers, views, or node handles.
  • Whether ordering, hashing, capacity growth, or allocation behavior affects the surrounding design.
  • Whether a non-owning view or a different container would express the real requirement more clearly.