public inbox for kawa@sourceware.org
 help / color / mirror / Atom feed
From: Duncan Mak <duncanmak@gmail.com>
To: Per Bothner <per@bothner.com>
Cc: kawa mailing list <kawa@sourceware.org>
Subject: Re: Supporting SRFI 43 (Vectors)
Date: Wed, 02 Jan 2019 03:38:00 -0000	[thread overview]
Message-ID: <CABgWrqqfYikQANRYw1GgBJ7ufJ0=nZHM5OqvrgvDcyrdmbhLCw@mail.gmail.com> (raw)
In-Reply-To: <a7eec044-9695-a8b2-1c6c-0dc4e77cacf4@bothner.com>

Okay, Here are the procedures that are missing:

= Constructors =
vector-unfold
vector-unfold-right
vector-reverse-copy
vector-concatenate

= Predicates =
vector-empty?
vector=

= Iteration =
vector-fold
vector-fold-right
vector-map!
vector-count

= Searching =
vector-index
vector-index-right
vector-skip
vector-skip-right
vector-binary-search
vector-any
vector-every

= Mutations =
vector-swap!
vector-reverse!
vector-reverse-copy!

= Conversion =
reverse-vector->list
reverse-list->vector

On Tue, Jan 1, 2019 at 8:27 PM Per Bothner <per@bothner.com> 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
> per@bothner.com   http://per.bothner.com/



-- 
Duncan.

  reply	other threads:[~2019-01-02  3:38 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 [this message]
2019-01-02 18:59     ` Duncan Mak

Reply instructions:

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:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='CABgWrqqfYikQANRYw1GgBJ7ufJ0=nZHM5OqvrgvDcyrdmbhLCw@mail.gmail.com' \
    --to=duncanmak@gmail.com \
    --cc=kawa@sourceware.org \
    --cc=per@bothner.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* 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).