Lightning Talk: Is Polymorphism in C++ Really That Bad?
summary
Case study of using polymorphism to unify many product variations for the small animal radiation research platform SARP claims inheritance plus composition and dependency injection meets requirements where per-hardware builds exploded. Naive design puts connection and control in one base Hardware class, causing pass-through shells; corrected design separates comms, uses Qt UI integration, considers std::variant and Concepts, marks classes final, measures runtime overhead and finds it small enough for the nonreal‑time workload and maintainable in production.
AI-written summary · about
related talks
01h 18mMeta Polymorphism
58mDeconstructing Inheritance
51mC++ Game Development - Many Ways to Kill an Orc (or a Hero)
59mPolymorphism with Unions
01h 03mPolicy-based design in C++20
05mDynaMix: A New Take on Polymorphism in C++
01h 01mC++ Design Patterns - The Most Common Misconceptions (2 of N)
01h 01mUsing Modern C++ to Eliminate Virtual Functions