> map (especially the new iterized version) is a frequently-used > builtin, while reduce is a rarely-used builtin that requires some > head-wrapping. It makes sense to me to move it out of builtins.
I've never understood this kind of argument. Because most people don't program in Python, we should abandon the project as a whole? For those who have "wrapped their head" around functional programming, "reduce" is a very clear and easy-to-understand primitive. But posting results gleaned from grepping over some random codebase written by someone who may or may not have done that head-wrapping at various points in time where some feature X may more may not have been available, seems even less of an argument. As I said, Guido's argument that "filter" (in the guise of [x for x in y if f(x)]), "any", and "all" are sufficient for almost every case seems like an interesting one to me, and he may well be right, but while we find out... Bill _______________________________________________ Python-3000 mailing list Python-3000@python.org http://mail.python.org/mailman/listinfo/python-3000 Unsubscribe: http://mail.python.org/mailman/options/python-3000/archive%40mail-archive.com
