From: Stefan Monnier <monnier@iro.umontreal.ca>
To: Po Lu <luangruo@yahoo.com>
Cc: emacs-devel@gnu.org
Subject: Re: Finalizers and incremental GC
Date: Fri, 03 Jun 2022 08:16:15 -0400 [thread overview]
Message-ID: <jwvv8tiymde.fsf-monnier+emacs@gnu.org> (raw)
In-Reply-To: <87ee0672hg.fsf@yahoo.com> (Po Lu's message of "Fri, 03 Jun 2022 13:14:19 +0800")
> Would it make more sense to run all the finalizers at once, after all
> white objects are swept and a garbage collection cycle completes, like
> the current garbage collector?
It shouldn't matter, so which ever is easiest or most efficient is
probably the better option. A secondary concern is to run the finalizers
as soon as possible.
IOW, what you do now is probably the better option,
Stefan
prev parent reply other threads:[~2022-06-03 12:16 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <87ee0672hg.fsf.ref@yahoo.com>
2022-06-03 5:14 ` Finalizers and incremental GC Po Lu
2022-06-03 12:16 ` Stefan Monnier [this message]
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=jwvv8tiymde.fsf-monnier+emacs@gnu.org \
--to=monnier@iro.umontreal.ca \
--cc=emacs-devel@gnu.org \
--cc=luangruo@yahoo.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).