|
vector->range issues
Wolfgang Corcoran-Mathe
(01 Sep 2020 19:21 UTC)
|
|
Re: vector->range issues
Marc Nieper-Wißkirchen
(01 Sep 2020 19:28 UTC)
|
|
Re: vector->range issues
Wolfgang Corcoran-Mathe
(01 Sep 2020 20:52 UTC)
|
|
Re: vector->range issues
Marc Nieper-Wißkirchen
(02 Sep 2020 05:48 UTC)
|
|
Re: vector->range issues
Marc Nieper-Wißkirchen
(02 Sep 2020 07:57 UTC)
|
|
string-range
Marc Nieper-Wißkirchen
(02 Sep 2020 13:14 UTC)
|
|
Re: string-range
Wolfgang Corcoran-Mathe
(02 Sep 2020 14:50 UTC)
|
|
Re: string-range
Marc Nieper-Wißkirchen
(02 Sep 2020 15:01 UTC)
|
|
Re: string-range
Wolfgang Corcoran-Mathe
(02 Sep 2020 15:56 UTC)
|
|
Re: string-range
Marc Nieper-Wißkirchen
(02 Sep 2020 15:58 UTC)
|
|
Re: string-range
John Cowan
(02 Sep 2020 21:12 UTC)
|
|
Re: string-range Wolfgang Corcoran-Mathe (02 Sep 2020 21:16 UTC)
|
|
Re: string-range
Wolfgang Corcoran-Mathe
(02 Sep 2020 21:25 UTC)
|
|
Re: vector->range issues
Wolfgang Corcoran-Mathe
(02 Sep 2020 14:46 UTC)
|
On 2020-09-02 17:11 -0400, John Cowan wrote: > > (define (string-range s) > > (vector-range (string->vector s))) > > > > This requires that string-range be O(n). Added. This is already in the current draft of the SRFI document. You may want to do a merge, then change whatever you don't like. > On testing: I think we should make sure that everything works with ranges > of length 0. Yes. I may also add some more tests to try and ensure that an implementation can't turn an empty range into a range with elements, since this violates the principle that all empty ranges are equal. The sample implementation consistently avoids this, I believe. -- Wolfgang Corcoran-Mathe <xxxxxx@sigwinch.xyz> "In the presence of the unknown all have an equal right to think." --Robert G. Ingersoll, "Individuality"
