Get App

Python: Which practice avoids a common mistake with collections.deque for Stacks and Queues?

Difficulty:

Medium

Questions:

1

Time Limit:

2 minutes

Passing Score:

100%

Question

Which practice avoids a common mistake with collections.deque for Stacks and Queues?

  1. Do not keep using a list for queue semantics once popleft-style behavior becomes central to correctness or performance.
  2. Ignore the collections.deque for Stacks and Queues issue and rely on team discipline instead of clearer APIs or invariants.
  3. Silence the collections.deque for Stacks and Queues problem by using broad catches, hidden globals, or extra shared mutable state.
  4. Prefer the version of collections.deque for Stacks and Queues 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 keep using a list for queue semantics once popleft-style behavior becomes central to correctness or performance.

Do not keep using a list for queue semantics once popleft-style behavior becomes central to correctness or performance. This is a common failure mode in real Python code and a frequent interview follow-up.

Track: Python