From: LdBeth <andpuke@foxmail.com>
To: Po Lu <luangruo@yahoo.com>
Cc: Stefan Monnier <monnier@iro.umontreal.ca>, emacs-devel@gnu.org
Subject: Re: Not using DOC for ELisp files
Date: Tue, 28 Dec 2021 12:11:22 +0800 [thread overview]
Message-ID: <tencent_4DB9B577273AB2F5606110EBB45B3DFCB90A@qq.com> (raw)
In-Reply-To: <871r1xzcrl.fsf@yahoo.com>
>>>>> In <871r1xzcrl.fsf@yahoo.com>
>>>>> Po Lu <luangruo@yahoo.com> wrote:
Po> BTW, while we're removing things like this, how about getting rid
Po> of pure space? Is it really necessary in this millennium, even
Po> for the unexec build?
Po> That should work without pure space, right?
Po> It would make the incremental garbage collector I'm slowly working
Po> towards somewhat simpler.
Having some data declared to be static can speed up GC scanning. It
does no longer really matter for sharing pure storage across different
emacs processes since today's emacsists get plenty of RAM IMO.
Probably that could be dropped in favor of a generational GC.
--
LDB
next prev parent reply other threads:[~2021-12-28 4:11 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-28 1:48 Not using DOC for ELisp files Stefan Monnier
2021-12-28 2:25 ` Po Lu
2021-12-28 3:48 ` Stefan Kangas
2021-12-28 5:39 ` Po Lu
2021-12-28 4:11 ` LdBeth [this message]
2021-12-28 5:03 ` Stefan Monnier
2021-12-28 5:38 ` Po Lu
2021-12-28 9:52 ` Phil Sainty
2021-12-28 10:31 ` Po Lu
2021-12-28 12:47 ` Po Lu
2021-12-28 7:10 ` Lars Ingebrigtsen
2021-12-28 3:39 ` Stefan Kangas
2021-12-28 5:10 ` Stefan Monnier
2021-12-28 6:56 ` Lars Ingebrigtsen
2021-12-28 12:44 ` Eli Zaretskii
2021-12-28 17:14 ` Stefan Monnier
2021-12-28 18:17 ` Eli Zaretskii
2021-12-29 0:15 ` Stefan Monnier
2021-12-29 12:30 ` Johann Klähn
2021-12-29 23:08 ` Stefan Monnier
2021-12-29 12:52 ` Eli Zaretskii
2021-12-29 23:23 ` Stefan Monnier
2021-12-30 7:20 ` Eli Zaretskii
2021-12-31 4:19 ` Stefan Monnier
2021-12-31 8:57 ` Eli Zaretskii
2021-12-31 16:16 ` Stefan Monnier
2021-12-31 18:45 ` Eli Zaretskii
2022-01-03 13:48 ` Ken Raeburn
2022-01-03 14:30 ` Eli Zaretskii
2022-01-07 22:59 ` Ken Raeburn
2022-01-08 7:08 ` Eli Zaretskii
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=tencent_4DB9B577273AB2F5606110EBB45B3DFCB90A@qq.com \
--to=andpuke@foxmail.com \
--cc=emacs-devel@gnu.org \
--cc=luangruo@yahoo.com \
--cc=monnier@iro.umontreal.ca \
/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).