From: Kevin Ryde <user42@zip.com.au>
Subject: Re: weak key hash versus display
Date: Sat, 01 Feb 2003 07:56:13 +1000 [thread overview]
Message-ID: <87vg05j85e.fsf@zip.com.au> (raw)
In-Reply-To: <xy7fzrbgf7g.fsf@nada.kth.se> (Mikael Djurfeldt's message of "Thu, 30 Jan 2003 10:27:31 +0100")
Mikael Djurfeldt <djurfeldt@nada.kth.se> writes:
>
> We should probably replace this vector with a weak vector, or (perhaps
> more efficient) clear the references from the vector.
Sounds wise, to avoid any chance of a program being badly bloated by
big structure kept around just because it was printed.
_______________________________________________
Bug-guile mailing list
Bug-guile@gnu.org
http://mail.gnu.org/mailman/listinfo/bug-guile
prev parent reply other threads:[~2003-01-31 21:56 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-01-29 23:21 weak key hash versus display Kevin Ryde
2003-01-30 9:27 ` Mikael Djurfeldt
2003-01-31 21:56 ` Kevin Ryde [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/guile/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87vg05j85e.fsf@zip.com.au \
--to=user42@zip.com.au \
/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).