From: Duncan Mak <firstname.lastname@example.org>
To: Per Bothner <email@example.com>
Cc: kawa mailing list <firstname.lastname@example.org>
Subject: Re: Supporting SRFI 43 (Vectors)
Date: Wed, 02 Jan 2019 18:59:00 -0000 [thread overview]
Message-ID: <CABgWrqrjjBJQ6xKG-vHZWxbULWHeh7fDbBbbHimtHQf2rX0V8g@mail.gmail.com> (raw)
Turns out there's a newer version of SRFI 43.
SRFI 43 standardized more vector procedures, all of which are included
in this SRFI. Unfortunately, R7RS-small and SRFI 43 placed
irreconcileable requirements on the procedures invoked by vector-map
and vector-for-each. This SRFI resolves that issue by changing these
SRFI 43 procedures as well as vector-map!, vector-fold,
vector-fold-right, and vector-count to leave out the index argument
that is passed under SRFI 43's definition.
On Tue, Jan 1, 2019 at 10:38 PM Duncan Mak <email@example.com> wrote:
> Okay, Here are the procedures that are missing:
> = Constructors =
> = Predicates =
> = Iteration =
> = Searching =
> = Mutations =
> = Conversion =
> On Tue, Jan 1, 2019 at 8:27 PM Per Bothner <firstname.lastname@example.org> wrote:
> > On 1/1/19 5:18 PM, Duncan Mak wrote:
> > > Hello all,
> > >
> > > As part of my project, I needed to use some APIs from SRFI 43 (vectors).
> > >
> > > I noticed that Kawa doesn't come with this SRFI, it has its own APIs
> > > for Vector (https://www.gnu.org/software/kawa/Vectors.html) and that
> > > is a subset of the entire SRFI 43 definition.
> > >
> > > In particular, I was missing vector-reverse-copy!
> > >
> > > What would it take to get SRFI 43 into the Kawa distribution?
> > I'll consider adding implementations for the missing procedures.
> > Initially on a procedure-by-procedure basis.
> > --
> > --Per Bothner
> > email@example.com http://per.bothner.com/
prev parent reply other threads:[~2019-01-02 18:59 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-02 1:19 Duncan Mak
2019-01-02 1:27 ` Per Bothner
2019-01-02 3:38 ` Duncan Mak
2019-01-02 18:59 ` Duncan Mak [this message]
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).