Google style guide bans map, reduce, and filter functions

>google style guide bans map, reduce, and filter functions
You told me functional programming was the next big thing Sup Forums.

I see no such prohibition in their C++ style guide.
Their Python style guide was written by this colossal stroopwafel-munching faggot and they haven't bothered changing it since he left.

everyone at google is a brainlet

You're fucking retarded there is no reason to use those functions in Python when list comprehensions are much more readable.

>reduce
>list comprehension

Reduce is a shitty unreadable mess.

with reduce you're supposed to use the for i in iterable construct
i'm assuming this is for python like the other guy and yeah, guido discourages those functions. why are you trying to code golf while using python anyways? it's not a functional language

>using basic functional features
>code golf

>doesn't allow more than one loop in a list comprehension

>smug anime girl
>using badly implemented high order functions in python because you're to intelligent to use haskell

Map is faster and more readable than a list comprehension in some cases.

in python? care to write a code snippet where that's the case and screenshot the times? because i don't believe you.

Fucking prove either of those claims

...

>range
Brainlet discovered. range has been deprecated for a while.

Ok I guess I stand corrected. I checked this for python3 (to address your range point), and I even did list(map(str, range(100))) to make sure it wasn't just making a lazy iterator, and I got ~25usec vs ~19usec.

Still faster using xrange.
In 3 map is lazy but it's faster than corresponding gen exp.

map is optimised in cpython to only load the function once, the comprehension has to load the str function from globals every iteration since you could modify it during iteration

>since you could modify it during iteration
When would this happen?

def f(x):
global str
def str(*_, **__):
print("fuck")
return X

[str(f(i)) for i in range(10)]

damn global keyword

The same could happen if you called a class method that modified that method when called

Actually map couldn't be optimised for this, only builtins