From: lloda <lloda@sarc.name>
To: "Thompson, David" <dthompson2@worcester.edu>
Cc: "Ludovic Courtès" <ludo@gnu.org>,
"Jean Abou Samra" <jean@abou-samra.fr>,
"guile-devel@gnu.org" <guile-devel@gnu.org>,
"Andy Wingo" <wingo@pobox.com>
Subject: Re: [EXT] [PATCH] Add 'bytevector-slice'.
Date: Wed, 11 Jan 2023 20:05:35 +0100 [thread overview]
Message-ID: <27DC75F6-8596-4B51-AA39-F6B76070B313@sarc.name> (raw)
In-Reply-To: <CAJ=RwfbnDyQbmH179P6FRePXWKRM6XzWYjma9fzwTVR7+D6Nzg@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 821 bytes --]
> On 11 Jan 2023, at 18:37, Thompson, David <dthompson2@worcester.edu> wrote:
>
> On Wed, Jan 11, 2023 at 12:34 PM Ludovic Courtès <ludo@gnu.org> wrote:
>>
>> What could be convenient though is ‘bytevector-copy’ (no bang), which
>> would combine ‘make-bytevector’ + ‘bytevector-copy!’.
>
> 'bytevector-copy' already exists, or do you mean some different
> implementation of it?
>
> - Dave
The current bytevector-copy takes a single argument. I would extend it in the same way the srfi4 copy functions were extended recently in the following commit
http://git.savannah.gnu.org/gitweb/?p=guile.git;a=commitdiff;h=6be51f9bbf47692ee5747b2cac6b372df65de970 <http://git.savannah.gnu.org/gitweb/?p=guile.git;a=commitdiff;h=6be51f9bbf47692ee5747b2cac6b372df65de970>
Regards
Daniel
[-- Attachment #2: Type: text/html, Size: 1588 bytes --]
next prev parent reply other threads:[~2023-01-11 19:05 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-11 15:00 [PATCH] Add 'bytevector-slice' Ludovic Courtès
2023-01-11 15:21 ` Thompson, David
2023-01-11 15:29 ` Jean Abou Samra
2023-01-11 17:34 ` Ludovic Courtès
2023-01-11 17:37 ` [EXT] " Thompson, David
2023-01-11 19:05 ` lloda [this message]
2023-01-12 22:27 ` [EXT] " Ludovic Courtès
2023-01-13 9:30 ` lloda
2023-01-11 17:39 ` The mysterious ‘SCM_F_BYTEVECTOR_CONTIGUOUS’ Ludovic Courtès
2023-01-11 18:51 ` lloda
2023-01-11 19:00 ` lloda
2023-01-12 0:10 ` [PATCH] Add 'bytevector-slice' Maxime Devos
2023-01-13 11:32 ` Ludovic Courtès
2023-01-13 11:56 ` Maxime Devos
2023-01-13 23:48 ` Ludovic Courtès
2023-01-14 14:45 ` Maxime Devos
2023-01-14 15:19 ` Ludovic Courtès
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
List information: https://www.gnu.org/software/guile/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=27DC75F6-8596-4B51-AA39-F6B76070B313@sarc.name \
--to=lloda@sarc.name \
--cc=dthompson2@worcester.edu \
--cc=guile-devel@gnu.org \
--cc=jean@abou-samra.fr \
--cc=ludo@gnu.org \
--cc=wingo@pobox.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).