Maybe something like passing in a list of patterns which should match some data, or a list of files/urls to download would be examples of where I would like to be generic, but taking in a string would be bad.
But the real solution be to convert it to foo(*args: str). But maybe if you take 2 Container[str] as input so you can't use *args. But no real world example comes to mind.
But what if you actually don't want str to be valid?
I know that Iterable and Collection aren't the same. My point is, that if you use Iterable[str] or Collection[str] as a more flexible alternative to list[str] you no longer have any type-hinting support protecting against passing in a plain string and you could end up with a subtle bug by unexpectedly looping over ['f', 'o', 'o'] instead of ['foo'].
Firefox, Neovim, Tmux, Various KDE applications, Nextcloud, Wine, Signal, OpenSSH
Probably many more
Die Synchronisierung ist nur manuell oder?
Re- not reverse-engineer.
Don't do this. Running unpatched software is a recipe for disaster.
It's a rather standard feature. Hardware and software have to be built/configured right for it to work well. That's what Valve did. I don't think there is any special sauce involved software wise.
Die Sonne ist KALT!
Yes, that's a good alternative for
Collection[str]but not so much forIterable[str]as you lose the lazyness of Generators.