The specification was copied verbatim (except for appropriate renaming) from
SRFI-135's textual-split by William Clinger:
https://srfi.schemers.org/srfi-135/srfi-135.html#textual-split

That doesn't really answer the question of what we should do, of course.
I haven't really through about, and don't have any strong (or otherwise) opinions.
SRFI-140 was intended as an alternative approach instead of SRFI-135, so I did a
lot of quick copy/paste/modify.

On 3/2/20 3:12 PM, Arthur A. Gleckler wrote:
> Per, would you please reply to this one as well?
>
> Thanks.
>
> On Mon, Nov 18, 2019 at 7:52 PM Chris Hanson <xxxxxx@chris-hanson.org <mailto:xxxxxx@chris-hanson.org>> wrote:
>
>     Sorry to be such a pest, but I found another unspecified behavior, this
>     time in string-split.
>
>     A problem arises if the delimiter has more than one character, and there
>     are overlapping matches for the delimiter.  For example, suppose the
>     delimiter is "aa" and the string is "faaab".  Does the delimiter match
>     the "aa" after "f", or the one before "b"?  It can't be both, and
>     choosing either seems arbitrary.
>
>     In any case, this should be addressed, either by explicitly saying it's
>     unspecified, or by specifying what should happen.
>

--
	--Per Bothner
xxxxxx@bothner.com   http://per.bothner.com/