[issue45856] [doc] map() documentation ambiguous about consumption order

Thibaut Horel added the comment: > this hasn't proven to be a point of confusion Absence of evidence is not evidence of absence… The word "confusion" is probably a bit strong, but I recently had to write code relying on this behavior and found myself checking the documentation to make sure

[issue45856] [doc] map() documentation ambiguous about consumption order

Raymond Hettinger added the comment: I don't think this suggestion is helpful or necessary. The map() docs have been around for a long time and this hasn't proven to be a point of confusion. The itertools docs already have a recipe demonstrating the technique of passing the same

[issue45856] [doc] map() documentation ambiguous about consumption order

Change by Raymond Hettinger : -- resolution: -> rejected stage: -> resolved status: open -> closed ___ Python tracker ___ ___

[issue45856] [doc] map() documentation ambiguous about consumption order

New submission from Thibaut Horel : In cases where multiple iterables are passed to the built-in function map(), the documentation is ambiguous about the order in which they are consumed [1]. Although the order of evaluation of function arguments is documented to be left-to-right in general