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 rhettinger
Recipients FR4NKESTI3N, kellerfuchs, mark.dickinson, rhettinger, serhiy.storchaka, steven.daprano, tim.peters
Date 2018-12-31.22:10:52
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1546294252.97.0.68830234216.issue35431@roundup.psfhosted.org>
In-reply-to
Content
Kellar and Yash, my suggestion is to separate the work into two phases.

Start with an initial patch that implements this simplest possible implementation, accompanied by clean documentation and thorough testing.

Once everyone has agreed on the API (i.e. calling it "comb()", how to handle various input datatypes, and handling of corner cases), and the patch is applied, only then turn to a second pass for optimizations (special casing various types, minimizing how big intermediate values can get by doing early cancellation, exploiting even/odd patterns etc).
History
Date User Action Args
2018-12-31 22:10:54rhettingersetrecipients: + rhettinger, tim.peters, mark.dickinson, steven.daprano, serhiy.storchaka, kellerfuchs, FR4NKESTI3N
2018-12-31 22:10:52rhettingersetmessageid: <1546294252.97.0.68830234216.issue35431@roundup.psfhosted.org>
2018-12-31 22:10:52rhettingerlinkissue35431 messages
2018-12-31 22:10:52rhettingercreate