Completed
Problem: One Definition Rule Violation
Class Central Classrooms beta
YouTube videos curated by Class Central.
Classroom Contents
Software Engineering Is About Tradeoffs
Automatically move to the next video in the Classroom when playback concludes
- 1 Intro
- 2 Problem Solving vs. Point of View
- 3 The cost of finding the best solution
- 4 std::string (simplified)
- 5 How often do you analyze exception safety of your code?
- 6 The importance of the Exception Safety Guarantees
- 7 Imagine the C++ Standard Library with only Basic Exception Safety Guarantee
- 8 Never-Empty Guarantee of Boost.Variant
- 9 Unit-Specific Aliases: Example
- 10 Quantity References: Example
- 11 User Defined Literals: Example
- 12 Standardization takes time
- 13 Comparison
- 14 One Definition Rule (ODR) - Translation Unit
- 15 One Definition Rule (ODR) - Program
- 16 Problem: One Definition Rule Violation
- 17 But this is how some customization points behave
- 18 Solution #1: Keep it as it is
- 19 Compile-time error when resulting dimension or unit is
- 20 Get rid of the Downcasting Facility
- 21 Designing is Hard
