From: Eli Zaretskii <eliz@gnu.org>
To: Stefan Monnier <monnier@iro.umontreal.ca>
Cc: troyhinckley@gmail.com, emacs-devel@gnu.org
Subject: Re: What happened to TCO?
Date: Thu, 18 Mar 2021 10:41:00 +0200 [thread overview]
Message-ID: <838s6kdfc3.fsf@gnu.org> (raw)
In-Reply-To: <jwva6r1gqiq.fsf-monnier+emacs@gnu.org> (message from Stefan Monnier on Wed, 17 Mar 2021 22:30:13 -0400)
> From: Stefan Monnier <monnier@iro.umontreal.ca>
> Date: Wed, 17 Mar 2021 22:30:13 -0400
> Cc: emacs-devel@gnu.org
>
> > I see two different patches from 2012
> > https://lists.gnu.org/archive/html/emacs-devel/2012-12/msg00283.html
> > https://lists.gnu.org/archive/html/emacs-devel/2012-09/msg00477.html
> > Neither was merged but I don't see any reason presented in the mailing
> > list. Why were these changes not accepted?
>
> I think the lukewarm reception discouraged them.
Maybe. This is for them to tell (and I hope that's not the case).
From where I stand, these two didn't go in because the discussion
wasn't followed-up to get to that "LGTM" point where we can land the
feature. Valid questions and considerations were brought up in each
of the two cases, but some of them were left unresolved. Stefan
mentioned some of them. In addition, I would like to remind us that
meanwhile we got the native-compilation feature, which is very close
to land on master, and one new question is how would these proposals
interact with it.
Feel free to respin one of those proposals based on current code, or
make some hybrid patch out of them. If and when the issues discussed
then are resolved, I think this optimization will be a welcome
addition to Emacs.
next prev parent reply other threads:[~2021-03-18 8:41 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-17 22:40 What happened to TCO? Troy Hinckley
2021-03-18 2:30 ` Stefan Monnier
2021-03-18 8:41 ` Eli Zaretskii [this message]
2021-03-18 10:01 ` Andrea Corallo via Emacs development discussions.
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=838s6kdfc3.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=monnier@iro.umontreal.ca \
--cc=troyhinckley@gmail.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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.