Software Design/Prohibit overriding implementation of a function

< Software Design

Why

Harder to reason about the behavior of a class if the function might be overridden in a subclass.
Fosters scattering the logic across the hierarchy => more navigation is required, easier to make mistakes because the logic of a procedure is not at the same place in front of the developer's eyes.

Why not

Forces to write boilerplate code (and leads to increased code size) when inheriting behavior from abstract classes (e. g. Java's default methods).
May lead to some logic duplication between implementations of a function in different classes extending an abstract class: see practice Don't repeat logic in several places.

Design and document for inheritance or else prohibit it

Sources

A De Goes, John (October 26, 2019). "12 Steps to Better Scala". Hamburg, Germany: Scala Hamburg. "Make Methods Final or Abstract"

Retrieved from "https://en.wikiversity.org/w/index.php?title=Software_Design/Prohibit_overriding_implementation_of_a_function&oldid=2092220"