From: Stefan Israelsson Tampe <stefan.itampe@gmail.com>
To: 24695@debbugs.gnu.org
Subject: bug#24695: impossible to use weak hash tables inside gc hooks
Date: Fri, 14 Oct 2016 20:54:56 +0200 [thread overview]
Message-ID: <CAGua6m3rdMOsnCNihhMn3Mbn2X9QiU5KFPv4HLdvK8tWbC=PBg@mail.gmail.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 441 bytes --]
For more advanced gc concepts it would be nice to keep a set a objects in a
weak key hash table and at gc loop over the alive ones the various gc hooks
that is available for the c coder.
The problem is that current guile data structure would hang on folding
because inside the guile weak folder gc is assumed to be prevented. Not
sure what to do here. This might be a feature request or a bug report
dependning on how you view it.
Regards
[-- Attachment #2: Type: text/html, Size: 511 bytes --]
next reply other threads:[~2016-10-14 18:54 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-14 18:54 Stefan Israelsson Tampe [this message]
2017-03-01 12:49 ` bug#24695: impossible to use weak hash tables inside gc hooks Andy Wingo
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='CAGua6m3rdMOsnCNihhMn3Mbn2X9QiU5KFPv4HLdvK8tWbC=PBg@mail.gmail.com' \
--to=stefan.itampe@gmail.com \
--cc=24695@debbugs.gnu.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.
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).