Additional procedure: array-assign! Bradley Lucier (24 Jan 2017 19:29 UTC)
Re: Additional procedure: array-assign! Arthur A. Gleckler (29 Jan 2017 18:34 UTC)
Re: Additional procedure: array-assign! Bradley Lucier (30 Jan 2017 21:25 UTC)
Re: Additional procedure: array-assign! Arthur A. Gleckler (31 Jan 2017 23:24 UTC)
Re: Additional procedure: array-assign! Bradley Lucier (01 Feb 2017 04:06 UTC)
Re: Additional procedure: array-assign! Arthur A. Gleckler (01 Feb 2017 05:37 UTC)

Re: Additional procedure: array-assign! Bradley Lucier 30 Jan 2017 21:25 UTC

On 01/29/2017 01:33 PM, Arthur A. Gleckler wrote:
> On Tue, Jan 24, 2017 at 11:29 AM, Bradley Lucier <xxxxxx@math.purdue.edu
> <mailto:xxxxxx@math.purdue.edu>> wrote:
>
>
>     I plan to add this procedure, documentation, and test code to my own
>     github repository.  If I could add it to the SRFI, I would, but I'm
>     content with just adding it to my own repository and marking it as
>     an "augmented" SRFI 122, or something like that.
>
>     What do people think?
>
>
> Since this isn't a bug in the spec., it's not appropriate for an
> erratum.  However, I would be happy to add a "post-finalization note" to
> the Status section and to include array-assign!in the reference
> implementation.  Would you mind sending me a patch or a pull request for
> that?

I've set something up in

https://github.com/gambiteer/srfi-122

and generated a pull request.  You may not be able to use it as is, but
perhaps it's something you can start with.

Tell me if you'd like something different.

Brad