From: Christopher Lemmer Webber <cwebber@dustycloud.org>
To: guile-devel@gnu.org
Cc: Andy Wingo <wingo@pobox.com>
Subject: Ephemerons, self-referentality in weak hashtables
Date: Tue, 18 May 2021 11:46:14 -0400 [thread overview]
Message-ID: <87czto11vd.fsf@dustycloud.org> (raw)
In-Reply-To: <87vb9ihy6x.fsf@igalia.com>
Hello,
I'm finally taking some time to port Goblins to Guile, in-between other
tasks anyway. In Goblins there is a weak hashtable that maps current
actor references to their current behavior. I found that for
self-referential actors, I needed ephemerons for GC stuff to work right.
In this old thread I found Wingo mentioning them:
Andy Wingo writes:
> * If there is a possibility of a path from B to A, you need an
> ephemeron table, and Guile doesn't do that right now. But it
> should!
Is there something ephemeron-like I should be doing?
next prev parent reply other threads:[~2021-05-18 15:46 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-04 10:10 Mark procedures Andy Wingo
2015-11-04 12:01 ` Stefan Israelsson Tampe
2015-11-04 17:01 ` Mark procedures, LilyPond, and backward compatibility Mark H Weaver
2015-11-05 10:16 ` Foreign object API Ludovic Courtès
2016-02-01 22:50 ` Foreign objects removed from ‘stable-2.0’ Ludovic Courtès
2015-11-05 14:46 ` Mark procedures, LilyPond, and backward compatibility Andy Wingo
2015-11-05 10:29 ` Mark procedures Ludovic Courtès
2015-11-05 13:11 ` Andy Wingo
2015-11-05 14:17 ` Ludovic Courtès
2015-11-06 12:32 ` Mark procedures and LilyPond Mark H Weaver
2015-11-06 13:50 ` Ludovic Courtès
2015-11-06 15:05 ` Stefan Monnier
2016-01-24 8:58 ` Hans Åberg
2016-06-20 10:34 ` Mark procedures Andy Wingo
2016-06-20 12:15 ` Ludovic Courtès
2021-05-18 15:46 ` Christopher Lemmer Webber [this message]
2021-06-20 15:01 ` Ephemerons, self-referentality in weak hashtables Maxime Devos
2021-06-21 17:15 ` Maxime Devos
2021-09-08 16:18 ` Christine Lemmer-Webber
2021-09-08 20:11 ` Maxime Devos
2021-09-08 20:50 ` Christine Lemmer-Webber
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/guile/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87czto11vd.fsf@dustycloud.org \
--to=cwebber@dustycloud.org \
--cc=guile-devel@gnu.org \
--cc=wingo@pobox.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.
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).