From c8507b349add4c6997ef67781585e14cd37c20c2 Mon Sep 17 00:00:00 2001 From: Thomas Grainger Date: Mon, 23 Sep 2019 19:02:16 +0100 Subject: [PATCH] Remove exception implying map or filter are ever acceptable --- ...using_map_or_filter_where_list_comprehension_is_possible.rst | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/readability/using_map_or_filter_where_list_comprehension_is_possible.rst b/docs/readability/using_map_or_filter_where_list_comprehension_is_possible.rst index edde9c4..f5c143f 100644 --- a/docs/readability/using_map_or_filter_where_list_comprehension_is_possible.rst +++ b/docs/readability/using_map_or_filter_where_list_comprehension_is_possible.rst @@ -1,7 +1,7 @@ Using ``map()`` or ``filter()`` where list comprehension is possible ==================================================================== -For simple transformations that can be expressed as a list comprehension, use list comprehensions over ``map()`` or ``filter()``. Use ``map()`` or ``filter()`` for expressions that are too long or complicated to express with a list comprehension. Although a ``map()`` or ``filter()`` expression may be functionally equivalent to a list comprehension, the list comprehension is generally more concise and easier to read. +For simple transformations that can be expressed as a list comprehension, use list comprehensions over ``map()`` or ``filter()``. Although a ``map()`` or ``filter()`` expression may be functionally equivalent to a list comprehension, the list comprehension is generally more concise and easier to read. Anti-pattern ------------