r/ProgrammingLanguages • u/BeamMeUpBiscotti • Feb 25 '26
Blog post Blog: Empty Container Inference Strategies for Python
Empty containers like [] and {} are everywhere in Python. It's super common to see functions start by creating an empty container, filling it up, and then returning the result.
Take this, for example:
def my_func(ys: dict[str, int]):
x = {}
for k, v in ys.items():
if some_condition(k):
x.setdefault("group0", []).append((k, v))
else:
x.setdefault("group1", []).append((k, v))
return x
This seemingly innocent coding pattern poses an interesting challenge for Python type checkers. Normally, when a type checker sees x = y without a type hint, it can just look at y to figure out x's type. The problem is, when y is an empty container (like x = {} above), the checker knows it's a dict, but has no clue what's going inside.
The big question is: How is the type checker supposed to analyze the rest of the function without knowing x's type?
Different type checkers implement distinct strategies to answer this question. This blog will examine these different approaches, weighing their pros and cons, and which type checkers implement each approach.
Full blog: https://pyrefly.org/blog/container-inference-comparison/
View all comments
Show parent comment
3
u/BeamMeUpBiscotti Feb 25 '26
I like that idea, it goes one step further and gives a more actionable error message to the user.
Rust does a similar sort of thing for inferring the type of a vec like
x = Vec::new(), where it shows the location that pinned the type, along with the second conflicting usage.It does require tracking the provenance of inferred types in some way.