These are different points. Just like you state a variable and some operations on it early in a comprehension, you do the same in a for loop: you don't know th

These are different points. Just like you state a variable and some operations on it early in a comprehension, you do the same in a for loop: you don't know the type of it. As you are typing the for loop in, your IDE does not know what is coming in as a context being iterated over to auto-complete, for instance (eg. imagine iterating over tuples with "for k, v in some_pairs:" — your editor does not even know if unpacking is possible). Basically, what I am saying is that comprehensions are similarly "bad" as for loops, except they are more powerful and allow more expression types early. C/C++ allow even crazier stuff in the "variable's" place in a for loop. Rust allows patterns, etc. Typing is mostly a nice addendum I mentioned, that's not the core of my point.