Really expose range-indexer? Marc Nieper-Wißkirchen (31 Aug 2020 18:35 UTC)
Re: Really expose range-indexer? Wolfgang Corcoran-Mathe (31 Aug 2020 19:11 UTC)
Re: Really expose range-indexer? Marc Nieper-Wißkirchen (31 Aug 2020 19:23 UTC)
Re: Really expose range-indexer? Marc Nieper-Wißkirchen (31 Aug 2020 19:31 UTC)
Re: Really expose range-indexer? John Cowan (01 Sep 2020 02:44 UTC)

Re: Really expose range-indexer? Marc Nieper-Wißkirchen 31 Aug 2020 19:22 UTC

Am Mo., 31. Aug. 2020 um 21:11 Uhr schrieb Wolfgang Corcoran-Mathe
<xxxxxx@sigwinch.xyz>:

> On 2020-08-31 20:35 +0200, Marc Nieper-Wißkirchen wrote:
> > As it is not clear to me what is a good use case of range-indexer
> > after all, I would consider dropping the procedure.
>
> Agreed.  It should be dropped.  I can't think of any reason to expose
> it, especially since some range operations return ranges whose indexers
> have unpredictable behavior on their own--i.e. without taking into
> account the `start-index' and `length' bounds of a range.

Conceptually all this means that a range is no more just a (logical)
pair consisting of a length and an indexer. Therefore, it may make
sense to rename

range => make-range

-- Marc