From: "Ludovic Courtès" <ludo@gnu.org>
To: Jean Abou Samra <jean@abou-samra.fr>
Cc: guile-devel@gnu.org, Andy Wingo <wingo@pobox.com>
Subject: Re: [PATCH] Add 'bytevector-slice'.
Date: Wed, 11 Jan 2023 18:34:12 +0100 [thread overview]
Message-ID: <87358hkmaz.fsf@gnu.org> (raw)
In-Reply-To: <fd5e511f-bf8d-5216-b40b-4522d5e11a49@abou-samra.fr> (Jean Abou Samra's message of "Wed, 11 Jan 2023 16:29:56 +0100")
Hi,
Jean Abou Samra <jean@abou-samra.fr> skribis:
> What do you think about making it more similar to substrings?
> There the 'substring' procedure makes a copy-on-write substring,
> and you have substring/shared if you really want shared mutation.
> Would something like this be meaningful / feasible / useful
> for bytevectors?
I’m not convinced there’s a need for copy-on-write bytevectors, and it
would be hard to implement, and to implement
efficiently—bytevector-mutating instructions would have to check whether
they’re accessing a CoW bytevector and DTRT.
What could be convenient though is ‘bytevector-copy’ (no bang), which
would combine ‘make-bytevector’ + ‘bytevector-copy!’.
Ludo’.
next prev parent reply other threads:[~2023-01-11 17:34 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 [this message]
2023-01-11 17:37 ` [EXT] " Thompson, David
2023-01-11 19:05 ` [EXT] " lloda
2023-01-12 22:27 ` 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=87358hkmaz.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=guile-devel@gnu.org \
--cc=jean@abou-samra.fr \
--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).