Type Hints · interview question
What is the clearest sign that code around optional and collections should be refactored?
Multiple choiceEasychapter-10-curatedpremiumtype-hintsoptional-and-collections
Answer and explanation
Correct answer
C. When the rule is no longer easy to trace, explain, or change without breaking nearby behavior.
Why
A refactor is justified when the code stops communicating its intent. Declare when values may be absent and when callers should expect lists, sets, or mappings of a certain shape.
Test yourself on Type Hints
A free test with instant, explained results. No account needed.
More Type Hints questions
- A teammate submits shaky typeddict and shaped data code. Which review comment is the strongest?
- Which explanation would best help the team align on function type hints?
- Which move is the best default when protocols becomes part of this workflow?
- When is protocols being used in the wrong way?
- What kind of contract clarity matters most for function type hints?
- When is optional and collections being used in the wrong way?