Question
Which practice avoids a common mistake with Monotonic Stack?
- Do not store only values when the problem really depends on positions or distances between elements.
- Ignore the Monotonic Stack issue and rely on team discipline instead of clearer APIs or invariants.
- Silence the Monotonic Stack problem by using broad catches, hidden globals, or extra shared mutable state.
- Prefer the version of Monotonic Stack that makes behavior less predictable as long as the code still runs.
Hint
Look for the option that protects correctness instead of hiding the problem.
Answer and rationale
Correct answer: A. Do not store only values when the problem really depends on positions or distances between elements.
Do not store only values when the problem really depends on positions or distances between elements. This is a common failure mode in real Python code and a frequent interview follow-up.
Track: Python