If you park in the street, and there are public chargers in a 1-km radius around your apartment, you can probably make it by "topping-up" every two or three days on a public charger.
Unless you spend upwards of 40% of your battery daily, you'll be good.
If you own a parking spot in your apartment complex, and depending on your jurisdiction, you can install your own charger.
You can even charge once a week or even less, depends on the usage.
You also don't have a gas station inside your apartment. Depending on which car you get, you could go charge it to charging station. I'm not saying this is instant process.
That's a poor excuse today. I'm not trying to be pushy but have you dismissed the LFP battery EVs? Those you charge fully once every other week, just like your average ICE vehicle. The time spent recharging can be spent grocery shopping or something else productive.
Based on the commit message and using "CL" which is google lingo for Change List on their internal system, I bet this was already available on the internal version and just ported to github version after someone pointed it out.
Much more prosaic (if slightly embarrassing), I'm afraid: The update was non-trivial (this CL is simple, but there are some accompanying ones in x/text which are not) and it didn't hit the top of the priority list for anyone who understands x/text.
Go is pretty much entirely developed in public; there are some Google-internal customizations but none of them are particularly exciting and almost all changes start in the open source repo and are imported from there.
"CL"/"Change List" is the lingo for the Gerrit code review tool, which is how all contributions to Go happen. Creating a GitHub PR simply triggers a bot to create a Gerrit CL, which is where all discussion about the "PR" happens and where the "accept" button gets clicked.
reply