From: Katsumi Yamaoka <yamaoka@jpl.org>
To: 19699@debbugs.gnu.org
Subject: bug#19699: 25.0.50; lexical-let + mapcar cause infloop
Date: Tue, 27 Jan 2015 17:06:44 +0900 [thread overview]
Message-ID: <b4mr3ug3awb.fsf@jpl.org> (raw)
A Lisp form that uses `lexical-let' and `mapcar' (or `mapc'),
like this, cannot be evaluated nor byte-compiled because it
looks like causing an infinite loop[1].
(defun testing ()
(lexical-let (var)
(mapcar #'identity '("Hello" "World"))))
[1] There is no means to stop infloop on Cygwin Emacs, so I'm
hard to debug it.
In GNU Emacs 25.0.50.1 (i686-pc-cygwin, GTK+ Version 3.10.9)
of 2015-01-27 on localhost
Windowing system distributor `The Cygwin/X Project', version 11.0.11501000
Configured using:
`configure --verbose --with-x-toolkit=gtk3'
next reply other threads:[~2015-01-27 8:06 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-27 8:06 Katsumi Yamaoka [this message]
2015-01-27 23:55 ` bug#19699: 25.0.50; lexical-let + mapcar cause infloop Katsumi Yamaoka
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=b4mr3ug3awb.fsf@jpl.org \
--to=yamaoka@jpl.org \
--cc=19699@debbugs.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.
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).