In this chapter's case study, we'll revisit our design, leveraging Python's
@dataclass definitions. This holds some potential for streamlining our design. We'll be looking at some choices and limitations; this will lead us to explore some difficult engineering trade-offs, where there isn't one obvious best approach.
We'll also look at immutable
NamedTuple class definitions. These objects have no internal state changes, leading to the possibility of some design simplifications. This will also change our design to make less use of inheritance and more use of composition.
Figure 7.2: Class diagram so far
Sample classes are a very good fit with the dataclass definition. These objects have a number...