From: Marius Vollmer <mvo@zagadka.de>
Subject: Re: doco hash tables
Date: Mon, 15 Sep 2003 15:48:29 +0200 [thread overview]
Message-ID: <87wucago2a.fsf@zagadka.ping.de> (raw)
In-Reply-To: <877k5dazob.fsf@zip.com.au> (Kevin Ryde's message of "Sun, 17 Aug 2003 10:35:48 +1000")
Kevin Ryde <user42@zip.com.au> writes:
> What can be said about the new resizing stuff and the initial size in
> make-hash-table? Is the initial size a permanent minimum, or just a
> hint? (I couldn't quite tell from the code.)
I don't know right away, but I say it is important to document
hashtables properly. Could you try to figure out what is going on and
document it? That would be super great.
--
GPG: D5D4E405 - 2F9B BCCC 8527 692A 04E3 331E FAF8 226A D5D4 E405
_______________________________________________
Guile-devel mailing list
Guile-devel@gnu.org
http://mail.gnu.org/mailman/listinfo/guile-devel
next prev parent reply other threads:[~2003-09-15 13:48 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-07-30 23:02 doco hash tables Kevin Ryde
2003-08-17 0:35 ` Kevin Ryde
2003-08-28 0:01 ` Kevin Ryde
2003-09-15 13:48 ` Marius Vollmer [this message]
2003-10-09 0:16 ` Kevin Ryde
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=87wucago2a.fsf@zagadka.ping.de \
--to=mvo@zagadka.de \
/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).