Liskov Substitution Principle
Version 1.0.0 · Updated 2026-07-30
CORE DEFINITION
Subclasses must be able to replace their base classes without causing errors in the program. That is, subclasses must not change the behavioral contract of the base class.
SCAFFOLDING EFFECT
Reduce cognitive load
Maintain contract consistency. If you promise a service (base class), your upgraded version (subclass) must be fully compatible with the old functionality, and must not secretly reduce or change behavior, otherwise it will break user trust (system crash).
Anchor fast decisions
The Liskov substitution principle requires that subclasses (subtypes) can seamlessly replace their base classes without breaking program correctness, meaning the behavioral contract must be compatible with the base class.
MINIMUM ACTION
In progress 0/1Practice this model in one real situation:
account_treeGenealogyexpand_more
menu_bookReferencesexpand_more
Source support: Explicit
- en.wikipedia.orghttps://en.wikipedia.org/wiki/Liskov_substitution_principleverified
PRIVATE NOTES · Only visible to you
SAVED Q&A
ENTRY Q&A · Private saving available
Ask with a clear boundary
thinkingmodels answers from published entry context only.
Your question is sent to thinkingmodels. The answer uses public entry context only.
RELATED MODELS