SRFI 196 ready for finalization?
John Cowan
(27 Jul 2020 22:57 UTC)
|
||
Re: SRFI 196 ready for finalization?
Wolfgang Corcoran-Mathe
(28 Jul 2020 00:24 UTC)
|
||
Re: SRFI 196 ready for finalization?
Marc Nieper-Wißkirchen
(29 Jul 2020 06:59 UTC)
|
||
Re: SRFI 196 ready for finalization?
John Cowan
(29 Jul 2020 14:32 UTC)
|
||
Re: SRFI 196 ready for finalization?
Wolfgang Corcoran-Mathe
(29 Jul 2020 17:52 UTC)
|
||
Re: SRFI 196 ready for finalization?
Wolfgang Corcoran-Mathe
(29 Jul 2020 18:56 UTC)
|
||
Re: SRFI 196 ready for finalization?
Arthur A. Gleckler
(30 Jul 2020 05:50 UTC)
|
||
Re: SRFI 196 ready for finalization?
Wolfgang Corcoran-Mathe
(30 Jul 2020 17:03 UTC)
|
||
Re: SRFI 196 ready for finalization?
Marc Nieper-Wißkirchen
(30 Jul 2020 18:34 UTC)
|
||
Re: SRFI 196 ready for finalization?
Arthur A. Gleckler
(30 Jul 2020 20:17 UTC)
|
||
Re: SRFI 196 ready for finalization?
John Cowan
(30 Jul 2020 23:44 UTC)
|
||
Re: SRFI 196 ready for finalization?
Marc Nieper-Wißkirchen
(31 Jul 2020 06:14 UTC)
|
||
Re: SRFI 196 ready for finalization?
Wolfgang Corcoran-Mathe
(31 Jul 2020 17:33 UTC)
|
||
Re: SRFI 196 ready for finalization?
Marc Nieper-Wißkirchen
(31 Jul 2020 18:01 UTC)
|
||
Re: SRFI 196 ready for finalization? Wolfgang Corcoran-Mathe (31 Jul 2020 18:49 UTC)
|
||
Re: SRFI 196 ready for finalization?
Marc Nieper-Wißkirchen
(01 Aug 2020 06:55 UTC)
|
||
Re: SRFI 196 ready for finalization?
John Cowan
(01 Aug 2020 17:20 UTC)
|
||
Re: SRFI 196 ready for finalization?
Marc Nieper-Wißkirchen
(01 Aug 2020 19:14 UTC)
|
||
Re: SRFI 196 ready for finalization?
Wolfgang Corcoran-Mathe
(04 Aug 2020 22:35 UTC)
|
||
(missing)
|
||
Fwd: SRFI 196 ready for finalization?
Marc Nieper-Wißkirchen
(26 Aug 2020 19:12 UTC)
|
||
Re: Fwd: SRFI 196 ready for finalization?
Wolfgang Corcoran-Mathe
(26 Aug 2020 21:03 UTC)
|
||
Re: SRFI 196 ready for finalization?
John Cowan
(05 Aug 2020 02:02 UTC)
|
||
Re: SRFI 196 ready for finalization?
John Cowan
(05 Aug 2020 02:28 UTC)
|
||
Re: SRFI 196 ready for finalization?
Wolfgang Corcoran-Mathe
(05 Aug 2020 02:35 UTC)
|
On 2020-07-31 20:01 +0200, Marc Nieper-Wißkirchen wrote: > Indeed, the solution is a composed indexer. I don't think it's that > bad as the algorithmic complexity wouldn't change. And as soon as we > have composed indexers, many more things become possible like > range-map. OK. If John concurs, we can remove the constraint on indexers and cherry-pick the earlier composed-indexer version of the sample implementation. > P.S.: It is possibly a good idea to allow abstract entities for > indexers and not only procedures. The problem is that procedures > (which are actually closures) cannot be introspected. This way, the > complexity can only increase when indexers are composed and the > implementation can never simplify indexers. To cure this, you have to > allow that range-indexer returns opaque values. This is an interesting idea, and would, I think, require very few changes to the sample implementation. John? -- Wolfgang Corcoran-Mathe <xxxxxx@sigwinch.xyz> "If work is to become play, then tools must become toys." --Lee Felsenstein