Behavioral Design Patterns in C++ - Generic Acycle Visitor - II

The video tutorial discusses optimizing Shape subclasses by removing boilerplate code for dynamic cost and introducing a base class called Visitable using the Curiously Recurring Template Pattern (CRTP). The Visitable class inherits from Shape and overrides the accept method. The tutorial also explains modifying the inheritance hierarchy, where Shape subclasses now inherit from Visitable. The video covers code cleanup, removing unnecessary files, and building the project. The final design structure is explained, highlighting the benefits of no circular dependency and allowing partial visitation.

What is the main purpose of introducing the Visitable class in the Shape hierarchy?

• To add more shapes easily

• To remove common boilerplate code

• To improve rendering performance

• To simplify the user interface

How does the Circle class change in the new inheritance hierarchy?

• It becomes a standalone class

• It inherits directly from Shape

• It inherits from the Visitable class

• It no longer exists

Which files are no longer required in the new build process?

• IO stream

• Line visitor and rectangle visitor CPP files

• Operation header file

• Shape header file

What is one of the benefits of the new design involving the Operation Visitor class?

• It increases the number of classes

• It introduces circular dependencies

• It allows partial visitation

• It complicates the code

What does the new design allow in terms of visitation?

• Full visitation of all shapes

• Visitation only for rectangles

• Partial visitation of selected shapes

• No visitation at all