Guidelines, Standards, and Community

Design and safety guidance

• C++ Core Guidelines: practical guidance on ownership, interfaces, safety, and maintainability.
• ISO C++ FAQ: concise answers to common language and design questions.

Standards-adjacent resources

• WG21 papers: proposal papers and committee working material.
• isocpp.org: news, standards information, and broader C++ community resources.

Best use cases

• Use the Core Guidelines when you need judgment about design tradeoffs rather than raw API syntax.
• Use WG21 papers when you want the rationale or evolution path behind a newer language or library feature.

When to start here

• you know the syntax already but need guidance on design quality or tradeoffs
• you want to understand why a feature exists, not just how it looks in code
• you need standards-adjacent material instead of day-to-day API lookup

Quick decision flow

1. Start with the Core Guidelines when the question is about ownership, interfaces, safety, or maintainability.
2. Open the ISO C++ FAQ when the question is common and you want a fast explanation.
3. Read WG21 papers when you need deeper rationale, feature evolution, or proposal background.

Practical guideline workflow

1. Start with the design problem in your own words: ownership, lifetime, API shape, error handling, or concurrency.
2. Scan the Core Guidelines for the relevant rule family.
3. Compare that guidance with the actual code you are reviewing or designing.
4. Only move to WG21 papers if you need the standardization rationale or newer feature context.

What each resource is best for

• Core Guidelines: day-to-day design review and refactoring decisions
• ISO C++ FAQ: fast clarification on common language and design questions
• WG21 papers: deeper rationale, proposal history, and feature tradeoffs
• isocpp.org: broader community context and standards-adjacent announcements