Why should std::env::var panic?

I discovered a similar issue with std::process::Command env handling:

This might be fixed along with this in a similar way (that would be least surprising for the user)