From: Michael Heerdegen <michael_heerdegen@web.de>
To: help-gnu-emacs@gnu.org
Subject: Re: Strange behavior related to byte-compiled files containing variables with hash-tables with lambdas
Date: Wed, 27 Jul 2022 01:30:01 +0200 [thread overview]
Message-ID: <87r127a1vq.fsf@web.de> (raw)
In-Reply-To: 21ef5189-7584-68be-5694-09819f97b30b@cvj.se
Christian Johansson <christian@cvj.se> writes:
> I have encountered strange behavior when byte-compiling files
> containing that have variables with hash-table entries with keys as
> strings and values are lambda-functions or lists of
> lambda-functions. The values are not the same between uncompiled or
> compiled or can't be worked with in the same way leading to strange
> bugs
>
> Do you know more about this? I encounter same issues in different
> Emacs version but right now I am using GNU Emacs 27.1
Do you have any recipe?
Michael.
next prev parent reply other threads:[~2022-07-26 23:30 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-26 5:04 Strange behavior related to byte-compiled files containing variables with hash-tables with lambdas Christian Johansson
2022-07-26 23:30 ` Michael Heerdegen [this message]
2022-07-29 15:57 ` Emanuel Berg
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=87r127a1vq.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).