From: Stefan Monnier <monnier@iro.umontreal.ca>
To: Daniel Colascione <dancol@dancol.org>
Cc: emacs-devel@gnu.org, Daniel Mendler <mail@daniel-mendler.de>
Subject: Re: Short functions
Date: Mon, 06 Jan 2025 12:25:27 -0500 [thread overview]
Message-ID: <jwv1pxfg8pg.fsf-monnier+emacs@gnu.org> (raw)
In-Reply-To: <6B4F0218-6692-4CD2-BECD-0C7CA047FC3E@dancol.org> (Daniel Colascione's message of "Mon, 06 Jan 2025 11:57:46 -0500")
>> more efficient, we'd want to avoid both heap allocation and recursion,
>> but sadly from ELisp the only way to allocate non-heap memory is via
>> recursion.
> Hopefully, generational GC will make heap allocation much less burdensome
> and the need for stack allocation (and escape analysis) less pressing.
+1 (and concurrent GC would also do the trick since we can generally
assume that there are free cycles available on another core)
Still, I keep hoping for a clever way to allow explicit avoidance of
heap allocation for those cases where the coder can be bothered to
make extra efforts for that.
Stefan
next prev parent reply other threads:[~2025-01-06 17:25 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <173617561349.1583674.17727386803499537943@vcs3.savannah.gnu.org>
[not found] ` <20250106150015.2A1DD1043A07@vcs3.savannah.gnu.org>
2025-01-06 15:55 ` [elpa] externals/consult 4aa49ee324 3/5: consult--async-pipeline: Convert to function Stefan Monnier
2025-01-06 16:09 ` Daniel Mendler via Emacs development discussions.
2025-01-06 16:52 ` Short functions (was: [elpa] externals/consult 4aa49ee324 3/5: consult--async-pipeline: Convert to function) Stefan Monnier
2025-01-06 16:57 ` Daniel Colascione
2025-01-06 17:25 ` Stefan Monnier [this message]
2025-01-06 17:32 ` Short functions Daniel Colascione
2025-01-06 17:02 ` Daniel Mendler via Emacs development discussions.
2025-01-06 17:13 ` Daniel Colascione
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=jwv1pxfg8pg.fsf-monnier+emacs@gnu.org \
--to=monnier@iro.umontreal.ca \
--cc=dancol@dancol.org \
--cc=emacs-devel@gnu.org \
--cc=mail@daniel-mendler.de \
/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).