OOP & Design Patterns - Liskov Substitution Principle - Subtype Behavioural Contract
When designing a framework that enforces LSP, what is a potential downside of using runtime checks to validate behavioral contracts?
When designing a framework that enforces LSP, what is a potential downside of using runtime checks to validate behavioral contracts?
medium🪤 Complexity Trap Q6 of Q15
Step-by-Step Solution
Solution:
Step 1: Understand runtime contract enforcement
Runtime checks can detect violations but add overhead and cannot replace compile-time guarantees.Step 2: Analyze options
A correctly identifies performance cost and incomplete coverage at compile time. B is false; runtime checks do not guarantee prevention before deployment. C and D are false; runtime checks do not simplify design or replace testing.Final Answer:
Option C -> Option CQuick Check:
Runtime checks add overhead and lack compile-time guarantees [OK]
Quick Trick: Runtime checks add overhead and miss compile-time errors [OK]
Common Mistakes:
MISTAKES- Believing runtime checks guarantee full contract safety
- Assuming runtime checks reduce design/testing effort
Trap Explanation:
PITFALL- Candidates overestimate runtime checks as a substitute for design discipline and testing.
Interviewer Note:
CONTEXT- Tests awareness of practical limitations in enforcing LSP dynamically.
Master "Liskov Substitution Principle - Subtype Behavioural Contract" in OOP & Design Patterns
Want More Practice?
15+ quiz questions · All difficulty levels · Free
Free Signup - Practice All QuestionsMore OOP & Design Patterns Quizzes