You’re right. But it is a factor of how much you drive. If you’re really down to ~10km/yr then you’re not the problem. Most of America, however, drives about 30km/yr. That kind of mileage adds up quickly with poor inefficient gigantobeast 4x4 dickreplacer500 trucks that are primarily used for grocery getters and work commuters. So EVs have their place - especially in that world.
When I originally typed it, I made a function for string reversal and called that. But I didn’t include it since I didn’t want to define that too.
Honestly… this wiki has a seriously difficult path ahead of it. I mean - it’d be fantastic if it did simplify things like that to let you write simple, elegant, and easy to read functions while linking to other functions.
But it’d also have to lint those and make sure that contributors don’t implement recursive dependencies.
Neat. I don’t like that the implementations have to name the function by some cryptic identifier, though. Real words matter in source code.
Who can tell me what this function is?
def Z10096(Z10096K1):
return Z10096K1 == Z10096K1[::-1]
How about this?
def isPalimdrone(myString):
return myString == myString[::-1]
It’s basically ThunderBolt 3 without the licensing.