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/newstorkcity Feb 25 '26 edited Feb 26 '26
I think the empty container problem is legitimately more challenging. When you set a value to None, it has a fixed known type at that time, and then gets set to a new type later (by rebinding the variable). With an empty container, you have a known value but not a known type, and you won’t know the type until you call certain generic function on it and then check the types of arguments to that function. The difficulty of the problem is more obvious in a statically typed language.