[Tim]
>> There's a difference, though: if `y` "leaks", BFD. Who cares? ;-)
>> If `y` remains inaccessible, there's no way around that.
> Part of it is just that people seem to be fighting for the sake of
> fighting. I'm weary of it, and I'm not going to debate this point with
> you. You want 'em to leak? No problem. Implement it that way and I'm
> not going to argue it.
I'm more interested in real-life use cases than in arguments. My
suggestion came from staring at my real-life use cases, where binding
expressions in comprehensions would clearly be more useful if the
names bound leaked. Nearly (but not all) of the time,, they're quite
happy with that for-target names don't leak. Those are matters of
observation rather than of argument.