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: Sun, 06 Nov 2022 01:39:42 +0100 [thread overview]
Message-ID: <874jvckjap.fsf@web.de> (raw)
In-Reply-To: 9b7534c5-90f7-49bd-235e-0cfbd0f1c81b@protonmail.com
Okamsn <okamsn@protonmail.com> writes:
> Is it possible to use `iter-yield` via mapping functions and `seq.el`
> functions? For example, when I do
>
> (setq iter-maker (iter-lambda (x)
> (seq-doseq (item x)
> (iter-yield item))))
> (setq my-iter (funcall iter-maker '(1 2 3)))
> (iter-next my-iter)
>
> I get an error "(void-function cps-internal-yield)".
Good question. `dolist' works. A rewrite using `mapc' doesn't (same
error).
Michael.
next prev parent reply other threads:[~2022-11-06 0:39 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 [this message]
2022-11-07 2:02 ` Michael Heerdegen
2022-11-07 12:31 ` Emanuel Berg
2022-11-07 14:08 ` Michael Heerdegen
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=874jvckjap.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).