Concept Driven Design with Dependency Injection
summary
Claims a workflow that uses C++14/17-era concepts emulation and policy-based design to wire dependencies at compile time, producing policy-based compile-time injection that compiles to static dispatch and smaller runtime overhead. Shows how printable/readable interfaces become concepts, how to opt out to a runtime path using Boost.Any or type erasure as runtime opt-out via any/type-erasure, and demonstrates easier unit tests by swapping implementations with the same concept. Source code lives on the linked GitHub.
AI-written summary · about
chapters (7)
related talks
01h 01mDependency Injection in C++ - A Practical Guide
01h 12mConcept Maps using C++23 Library Tech - Indirection to APIs for a Concept
01h 29mDependency Injection in C++ - A Practical Guide
58mA Practical Guide to Loose Coupling
01h 28mLaw of Demeter: A Practical Guide to Loose Coupling
01h 07mC++20 Concepts: A Day in the Life
58mConcept Based Testing
32mCompile- and Run-Time Dependency Injection