Email list hosting service & mailing list manager

relationship to SRFI-25 Per Bothner (30 Jul 2015 05:30 UTC)
Re: relationship to SRFI-25 John Cowan (30 Jul 2015 20:20 UTC)
Re: relationship to SRFI-25 Bradley Lucier (31 Jul 2015 21:00 UTC)
Re: relationship to SRFI-25 Bradley Lucier (26 Sep 2015 18:33 UTC)
Re: relationship to SRFI-25 Per Bothner (27 Sep 2015 05:34 UTC)
Re: relationship to SRFI-25 Bradley Lucier (28 Sep 2015 21:04 UTC)
Re: relationship to SRFI-25 Per Bothner (28 Sep 2015 21:29 UTC)
Re: relationship to SRFI-25 Bradley Lucier (28 Sep 2015 21:54 UTC)
Re: relationship to SRFI-25 Jamison Hope (28 Sep 2015 22:22 UTC)
Re: relationship to SRFI-25 Bradley Lucier (28 Sep 2015 22:38 UTC)
Re: relationship to SRFI-25 Jamison Hope (28 Sep 2015 23:20 UTC)
Re: relationship to SRFI-25 Bradley Lucier (29 Sep 2015 06:03 UTC)
Re: relationship to SRFI-25 Jamison Hope (29 Sep 2015 16:12 UTC)
Re: relationship to SRFI-25 Bradley Lucier (30 Sep 2015 03:42 UTC)

Re: relationship to SRFI-25 Bradley Lucier 29 Sep 2015 06:03 UTC

On 09/28/2015 07:20 PM, Jamison Hope wrote:
't really understand this part.
>
> I'm not suggesting that array-map be implemented on top of array-ref,
> or that whatever other mutating functions there are be implemented
> on top of array-set! -- just that as an end user, having to extract
> and then invoke a closure rather than just calling a setter or getter
> *function* seems strange.

OK.

Often, there is only the getter function.  (I'm not sure what
distinction you're trying to make when you call it a "closure".)

I implement zero scalar fields over various domains as

(array domain (lambda (i j) 0.))

So one has only the getter function to work with, so if one wants to write

(array-ref a i j)

one actually needs to call ((array-getter a) i j)

Brad