From: Stefan Monnier via Users list for the GNU Emacs text editor <help-gnu-emacs@gnu.org>
To: help-gnu-emacs@gnu.org
Subject: Re: How to specialize seq-concatenate and seq-into-sequence?
Date: Fri, 04 Mar 2022 18:02:00 -0500 [thread overview]
Message-ID: <jwvee3hnwzj.fsf-monnier+emacs@gnu.org> (raw)
In-Reply-To: 87r17hgyf2.fsf@web.de
> Why `seq-do'?
To avoid allocating intermediate sequences.
But yes, there are other solutions, with different tradeoffs.
Stefan
next prev parent reply other threads:[~2022-03-04 23:02 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-03 15:50 How to specialize seq-concatenate and seq-into-sequence? Philipp Stephani
2022-03-03 17:40 ` Stefan Monnier via Users list for the GNU Emacs text editor
2022-03-03 20:49 ` Philipp Stephani
2022-03-04 0:20 ` Stefan Monnier
2022-03-04 0:48 ` Philipp Stephani
2022-03-04 2:35 ` Michael Heerdegen
2022-03-04 14:31 ` Stefan Monnier via Users list for the GNU Emacs text editor
2022-03-04 22:12 ` Michael Heerdegen
2022-03-04 23:02 ` Stefan Monnier via Users list for the GNU Emacs text editor [this message]
2022-03-04 20:56 ` Philipp Stephani
2022-03-04 21:54 ` Michael Heerdegen
2022-03-04 13:31 ` Stefan Monnier
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=jwvee3hnwzj.fsf-monnier+emacs@gnu.org \
--to=help-gnu-emacs@gnu.org \
--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.
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).