Language and Standard Library
Language and Standard Library
Fast-reference links for core language rules, standard-library APIs, headers, and everyday lookup work.
Language and Standard Library
Primary lookup sites
Best use cases
- Use cppreference for quick checks of signatures, iterator invalidation, complexity, feature-test macros, and header relationships.
- Use vendor library docs when behavior, implementation notes, or platform integration details matter.
Practical habit
- Keep one reference tab open while reading handbook pages so you can cross-check APIs without losing context.
When to start here
- you need fast confirmation of a signature, header, complexity rule, or invalidation note
- you are comparing handbook guidance with an authoritative library or language reference
- you want a vendor-specific library note after checking the general rule first
Fast lookup workflow
- Start with cppreference for the general rule, signature, or header.
- Check vendor docs when the issue involves implementation notes, platform behavior, or ecosystem-specific guidance.
- Return to the handbook when you want the broader teaching context or surrounding tradeoffs.
What to look up first
- header name and required include
- complexity guarantees and iterator invalidation notes
- value-category, ownership, and lifetime expectations
- feature-test macros or standard-version availability when using newer facilities
Fast library-reference habit
If you are checking a container, scan construction, modifier operations, invalidation, and lookup complexity before writing code. If you are checking a vocabulary type, scan ownership or error-transport semantics before looking at helper members.
Language-rule workflow
- Use the handbook page to frame the topic and major tradeoffs.
- Use cppreference to confirm exact syntax, guarantees, and edge cases.
- Verify the rule in a tiny local program when the consequence affects performance, overload resolution, or lifetime.