Author tim.peters
Recipients Springem Springsbee, terry.reedy, tim.peters, xtreak
Date 2018-10-26.21:08:46
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1540588126.84.0.788709270274.issue35079@psf.upfronthosting.co.za>
In-reply-to
Content
I don't object to spelling it out more, and your (Terry's) suggestions are fine.  On the other hand, this module has been around for a loooong time now, and this is the first instance I've seen of someone surprised that it doesn't produce overlapping matches - it's obvious from "The same idea is then applied recursively to the pieces of the sequences to the left and to the right of the matching subsequence" that a matching subsequence is wholly eliminated from further consideration.

At some point of ever-more tedious elaboration, the docs risk missing the forest for the trees.  I don't think _these_ docs are quite there yet - although the docs for `find_longest_match()` are.  Speaking of which, that method _could_ be used to find overlapping matches, one at a time, by passing appropriate slice indices.

Which can be horridly inefficient; e.g., find all overlapping matches between

'A' * 100

and

'A' * 150
History
Date User Action Args
2018-10-26 21:08:46tim.peterssetrecipients: + tim.peters, terry.reedy, xtreak, Springem Springsbee
2018-10-26 21:08:46tim.peterssetmessageid: <1540588126.84.0.788709270274.issue35079@psf.upfronthosting.co.za>
2018-10-26 21:08:46tim.peterslinkissue35079 messages
2018-10-26 21:08:46tim.peterscreate