Question
When should a Python developer choose Mutable Default Arguments deliberately?
- Choose Mutable Default Arguments mainly when you want to postpone validation and fix issues manually later.
- Choose Mutable Default Arguments whenever you want the code to look more advanced, even if the design gets less clear.
- Choose Mutable Default Arguments only to avoid modeling the real data shape or domain contract explicitly.
- Choose a sentinel such as None when the function needs a fresh list or dict for each invocation.
Hint
Think about the production scenario where the choice genuinely improves the code.
Answer and rationale
Correct answer: D. Choose a sentinel such as None when the function needs a fresh list or dict for each invocation.
Choose a sentinel such as None when the function needs a fresh list or dict for each invocation. Interviewers often ask this to see whether you can connect the concept to real design decisions.
Track: Python