From: Lars Ingebrigtsen <larsi@gnus.org>
To: Stefan Monnier <monnier@iro.umontreal.ca>
Cc: 26629@debbugs.gnu.org, Tobias Zawada <i@tn-home.de>
Subject: bug#26629: 25.1.50; Feature-request: Structure-preserving copying of sequences
Date: Sat, 14 May 2022 04:18:36 +0200 [thread overview]
Message-ID: <875ym8eu0z.fsf@gnus.org> (raw)
In-Reply-To: <jwv8rr5jpmx.fsf-monnier+emacs@gnu.org> (Stefan Monnier's message of "Fri, 13 May 2022 13:47:53 -0400")
Stefan Monnier <monnier@iro.umontreal.ca> writes:
> So rather than `copy-tree*` I'd rather see some kind of generic
> `deep-copy` function which takes a (or some) parameter(s) that indicates
> when (and potentially how) to copy/recurse each of the elements (where
> `deep-copy`s job would thus be mainly to take care of maintaining the
> hash-map and maybe using an explicit stack to avoid deep recursion).
Makes sense to me. Since we're not going to include `copy-tree*' (being
too niche), I'm closing this bug report, but a more general `deep-copy'
function would be welcome, if somebody were to write it.
--
(domestic pets only, the antidote for overdose, milk.)
bloggy blog: http://lars.ingebrigtsen.no
prev parent reply other threads:[~2022-05-14 2:18 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-23 22:02 bug#26629: 25.1.50; Feature-request: Structure-preserving copying of sequences Tobias Zawada
2022-05-13 16:18 ` Lars Ingebrigtsen
2022-05-13 17:47 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-05-14 2:18 ` Lars Ingebrigtsen [this message]
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/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=875ym8eu0z.fsf@gnus.org \
--to=larsi@gnus.org \
--cc=26629@debbugs.gnu.org \
--cc=i@tn-home.de \
--cc=monnier@iro.umontreal.ca \
/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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs.git
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).