From: Michael Heerdegen <michael_heerdegen@web.de>
To: help-gnu-emacs@gnu.org
Subject: Re: Using `iter-yield` with `seq.el` and mapping functions?
Date: Mon, 07 Nov 2022 15:08:55 +0100 [thread overview]
Message-ID: <871qqen9fs.fsf@web.de> (raw)
In-Reply-To: 87fsevq73p.fsf@dataswamp.org
Emanuel Berg <incal@dataswamp.org> writes:
> Michael Heerdegen wrote:
>
> > (iter-next
> > (funcall
> > (iter-lambda (l)
> > (dolist (y l) (iter-yield y)))
> > '(1 2 3)))
>
> Hm, what's the advantage or increased expressibility with
> this method?
Do you ask about the purpose of using iterators, or do you ask why the
above call doesn't error like the one having the issue?
Michael.
next prev parent reply other threads:[~2022-11-07 14:08 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-05 21:28 Using `iter-yield` with `seq.el` and mapping functions? Okamsn
2022-11-06 0:39 ` Michael Heerdegen
2022-11-07 2:02 ` Michael Heerdegen
2022-11-07 12:31 ` Emanuel Berg
2022-11-07 14:08 ` Michael Heerdegen [this message]
2022-11-07 16:50 ` Emanuel Berg
2022-11-08 22:45 ` Michael Heerdegen
2022-11-09 1:29 ` Michael Heerdegen
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=871qqen9fs.fsf@web.de \
--to=michael_heerdegen@web.de \
--cc=help-gnu-emacs@gnu.org \
/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).