C++ (Core) Guidelines - Safer C++
summary
Ten years of IDE work produce a concrete toolset inside Cevelop that finds core-guideline violations and offers automatic repair like inserting const correctness and converting to Rule-of-Zero patterns with quick-fix refactorings. The implementation covers RAII, unique_ptr adoption, switch-fallthrough fixes and standard-algorithm suggestions; it flags non-owning vs owning pointers but warns that owner<T> is inferior to immediate unique_ptr refactoring. Some rules cannot be adopted incrementally and not all C++17/20 items are implemented yet.
AI-written summary · about
chapters (24)
- 0:00Introduction
- 1:38Lifetime goal
- 2:07What are guidelines
- 4:00Guidelines landscape
- 7:27Role of guidelines
- 10:41Undefined behavior
- 11:17Bad corners
- 16:15Good practices
- 16:43Core Guidelines
- 18:53Examples
- 27:51Philosophy behind the Guidelines
- 28:50Myths
- 31:23Interfaces
- 32:42Constructors
- 34:16Default of Operations
- 34:57Move Assignments
- 37:44League Resources
- 39:06Multiple Resources
- 40:08Ownership
- 41:38Cons
- 42:28Classes
- 43:25Support Library
- 44:59RevUp
- 46:15Questions
related talks
27mThe Core C++ Guidelines for Safer Code
54mType-and-resource Safety in Modern C++
51mSecure Programming Practices in C++
57mThe Misra C++:2023 Guidelines
50mSecure development with C++ - Lessons and techniques
01h 20mSafer C++: MISRA-C++ : 202X Rules and Beyond
58mMisra Parallelism Safety-critical Guidelines for C++11, 17, Then C++20, 23
01h 02mModern C++ Safety and Security At 20