unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Andrea Corallo via "Bug reports for GNU Emacs, the Swiss army knife of text editors" <bug-gnu-emacs@gnu.org>
To: "Mark A. Hershberger" <mah@nichework.com>
Cc: 45056@debbugs.gnu.org
Subject: bug#45056: 28.0.50; lexical-let doesn't work with returned closures on nativecomp
Date: Tue, 08 Dec 2020 21:28:12 +0000	[thread overview]
Message-ID: <xjf1rg00yz7.fsf@sdf.org> (raw)
In-Reply-To: <87pn3kgh81.fsf@everybody.org> (Mark A. Hershberger's message of "Tue, 08 Dec 2020 15:45:02 -0500")

"Mark A. Hershberger" <mah@nichework.com> writes:

> I just spent some time attempting to create a minimal test case using a
> new user and some stripped down init.el, but couldn't reproduce it.
>
> For now, I'm going to have to assume that the problem I'm seeing with
> the lexical-let is a side-effect of some other problems my nativecomp
> emacs is exhibiting (use-packages are acting funny).

Hi Mark,

thanks for checking.

The lexical-let is not creating a real closure or anything else bizarre
from a compiler prespective, so I'd be surprised if we misscompile it.
If you see an overall different behaviour I'd bet on something else.

My suggestion would be to close this bug an open a new dedicated one
when we a get a reproducer to investigate on?

As you prefer.

Thanks

  Andrea





  reply	other threads:[~2020-12-08 21:28 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-12-05 18:16 bug#45056: 28.0.50; lexical-let doesn't work with returned closures on nativecomp Mark A. Hershberger via Bug reports for GNU Emacs, the Swiss army knife of text editors
2020-12-05 19:49 ` Andrea Corallo via Bug reports for GNU Emacs, the Swiss army knife of text editors
2020-12-05 21:21   ` Mark A. Hershberger
2020-12-05 21:57     ` Mark A. Hershberger
2020-12-05 22:06       ` Andrea Corallo via Bug reports for GNU Emacs, the Swiss army knife of text editors
2020-12-06  0:26         ` Mark A. Hershberger
2020-12-06 10:33           ` Andrea Corallo via Bug reports for GNU Emacs, the Swiss army knife of text editors
2020-12-06 19:55             ` Mark A. Hershberger
2020-12-07 15:45               ` Andrea Corallo via Bug reports for GNU Emacs, the Swiss army knife of text editors
2020-12-08 14:59                 ` Mark A. Hershberger
2020-12-08 15:18                   ` Andrea Corallo via Bug reports for GNU Emacs, the Swiss army knife of text editors
2020-12-08 20:45                     ` Mark A. Hershberger
2020-12-08 21:28                       ` Andrea Corallo via Bug reports for GNU Emacs, the Swiss army knife of text editors [this message]
2020-12-08 21:42                         ` Mark A. Hershberger
2020-12-08 22:21                           ` Andrea Corallo via Bug reports for GNU Emacs, the Swiss army knife of text editors
2020-12-29 22:06                             ` Mark A. Hershberger

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=xjf1rg00yz7.fsf@sdf.org \
    --to=bug-gnu-emacs@gnu.org \
    --cc=45056@debbugs.gnu.org \
    --cc=akrl@sdf.org \
    --cc=mah@nichework.com \
    /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).