This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author loewis
Recipients hynek, loewis, lukasz.langa, ncoghlan, rhettinger, serhiy.storchaka
Date 2013-08-04.12:14:26
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1375618466.68.0.538218853272.issue18652@psf.upfronthosting.co.za>
In-reply-to
Content
Simplicity is in the eye of the beholder, yet... you need to remember the break when *writing* the code, so the loop might be more difficult to write (but then, I need to remember/lookup the function name and parameters for coalesce)... when reading the code, the break is already there, and easy to notice. With Nick's remark, it's even more obvious that it is difficult to write :-)

If an unknown (to the reader) function is used, reading the code becomes actually difficult, since the reader either needs to guess what the function does, or look it up.

Note that I'm not objecting the addition of the function (I'm neutral), just the claim that there are no simple alternatives. I'm neutral because it falls under the "not every two-line function needs to go into the standard library" rule; but then, if it is really popular, it helps readability if it is in the library (rather than duplicated by users).
History
Date User Action Args
2013-08-04 12:14:26loewissetrecipients: + loewis, rhettinger, ncoghlan, lukasz.langa, hynek, serhiy.storchaka
2013-08-04 12:14:26loewissetmessageid: <1375618466.68.0.538218853272.issue18652@psf.upfronthosting.co.za>
2013-08-04 12:14:26loewislinkissue18652 messages
2013-08-04 12:14:26loewiscreate