Writing Good C++14
summary
Practical rules for using C++14 aim to eliminate leaks, dangling pointers, and many type errors by pairing 350+ concrete checks with small library types and static analysis. A tiny MIT-licensed Guideline Support Library on GitHub supplies owner/non-owner annotations plus not_null and array_view helpers; a Microsoft-backed static-analysis tool is due to ship next month. Claim: combining prescriptive rules, checkable annotations, and tooling can cut common C++ errors dramatically and speed modernization of large codebases.
AI-written summary · about
chapters (18)
- 0:00Introduction to the project
- 4:20Project goals and philosophy
- 8:23Challenges with traditional rules
- 12:33Designing better guidelines
- 14:35Structure of the rules
- 17:41The superset approach
- 20:45Expected benefits
- 24:16Focusing on core safety
- 25:43Solving the dangling pointer problem
- 29:49Representing ownership
- 33:44Enforcing safety through tools
- 36:42Improving common C++ patterns
- 41:31Refining pointer usage
- 45:01Standardization and tooling
- 47:08Managing rule complexity
- 50:57Future outlook and collaboration
- 54:01Project status and conclusion
- 56:45Q&A session
related talks
01h 29mC++ Core Guidelines - Modernize your C++ Code Base
55mC++ Core and Other C++ Guidelines - The Good, the Bad, the… Questionable?
01h 34mC++11/14 at Scale - What Have We Learned?
01h 36mBuilding C++ Interfaces That Are Hard to Use Incorrectly
01h 01mThe Best Parts of C++
19mC++ Const Correctness Refresher
01h 28mKeynote: Safety, Security, Safety and C / C++ - C++ Evolution
54mA look at C++ through the glasses of a language tool