all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Lars Ingebrigtsen <larsi@gnus.org>
Cc: 34404@debbugs.gnu.org, braungb88@gmail.com
Subject: bug#34404: 26.1; Finalizer in hash table run early?
Date: Fri, 27 Nov 2020 10:42:23 +0200	[thread overview]
Message-ID: <83blfjp4wg.fsf@gnu.org> (raw)
In-Reply-To: <87tutbjj1w.fsf@gnus.org> (message from Lars Ingebrigtsen on Fri,  27 Nov 2020 09:33:15 +0100)

> From: Lars Ingebrigtsen <larsi@gnus.org>
> Cc: rudalics@gmx.at,  34404@debbugs.gnu.org,  braungb88@gmail.com
> Date: Fri, 27 Nov 2020 09:33:15 +0100
> 
> Eli Zaretskii <eliz@gnu.org> writes:
> 
> > The question is how do you define "100%"?  The Emacs GC is
> > conservative in the sense that when there's a doubt whether an object
> > _could_ be still referenced, we mark it so it doesn't get swept.
> 
> When is Emacs in doubt?  :-)

Mainly when we find what looks like Lisp objects on the C stack.

> If we could say something about this in the manual (or the
> `garbage-collect' doc string), I think that'd be helpful -- people
> do seem to think that calling `garbage-collect' is guaranteed to
> collect all the garbage.

Fine by me, please feel free to suggest such wording.





  reply	other threads:[~2020-11-27  8:42 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-02-09 13:39 bug#34404: 26.1; Finalizer in hash table run early? Braun Gábor
2020-11-26 12:15 ` Lars Ingebrigtsen
2020-11-26 12:54   ` Andreas Schwab
2020-11-26 14:23   ` Eli Zaretskii
2020-11-26 15:45   ` martin rudalics
2020-11-27  7:56     ` Lars Ingebrigtsen
2020-11-27  8:23       ` Eli Zaretskii
2020-11-27  8:33         ` Lars Ingebrigtsen
2020-11-27  8:42           ` Eli Zaretskii [this message]
2020-11-29 10:05             ` Lars Ingebrigtsen

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=83blfjp4wg.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=34404@debbugs.gnu.org \
    --cc=braungb88@gmail.com \
    --cc=larsi@gnus.org \
    /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.