|
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)
|
Am Mi., 2. Sept. 2020 um 17:56 Uhr schrieb Wolfgang Corcoran-Mathe <xxxxxx@sigwinch.xyz>: > For completeness, yes, this should be added, since vector-range has > range->vector, etc. Hopefully this will be it for additional > conversions and constructors. I don't think bytevector ranges would be of much use. ;)
