From: Gregory Marton <gremio@mit.edu>
To: Neil Jerram <INVALID.NOREPLY@gnu.org>
Cc: bug-guile@gnu.org, Neil Jerram <neil@ossau.uklinux.net>
Subject: Re: [bug #22022] hashx-set! and -ref
Date: Thu, 17 Jan 2008 17:01:16 -0500 (EST) [thread overview]
Message-ID: <Pine.LNX.4.62.0801171659460.6868@ashmore.csail.mit.edu> (raw)
In-Reply-To: <20080117-215736.sv185.71494@savannah.gnu.org>
Thanks, yes. I initially had a one in there. Hmmm... it doesn't matter.
33 is enough to trigger resize.
Thanks,
Grem
> Follow-up Comment #2, bug #22022 (project guile):
>
> Another one:
>
> (pass-if (equal? "#<hash-table 34/61>"
> (with-output-to-string (lambda () (write table)))))))
>
> Actual output here has 33 instead of 34. I believe 33 is correct, because
> the additions to the hash table run from 2 up to 34, not from 1 up to 34.
>
> Agree?
>
> _______________________________________________________
>
> Reply to this item at:
>
> <http://savannah.gnu.org/bugs/?22022>
>
> _______________________________________________
> Message sent via/by Savannah
> http://savannah.gnu.org/
>
>
>
>
--
------ __@ Gregory A. Marton http://csail.mit.edu/~gremio/
--- _`\<,_ .
-- (*)/ (*) Teach you backwards to speak I can.
~~~~~~~~~~~~~~~~-~~~~~~~~_~~~_~~~~~v~~~~^^^^~~~~~--~~~~~~~~~~~~~~~++~~~~~~~
next prev parent reply other threads:[~2008-01-17 22:01 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-01-14 22:40 [bug #22022] hashx-set! and -ref Gregory Marton
2008-01-17 21:52 ` Neil Jerram
2008-01-17 21:54 ` Gregory Marton
2008-01-17 23:02 ` Neil Jerram
2008-01-18 0:25 ` Gregory Marton
2008-01-17 21:57 ` Neil Jerram
2008-01-17 22:01 ` Gregory Marton [this message]
2008-01-17 22:45 ` Neil Jerram
2008-01-18 0:22 ` Gregory Marton
2008-01-29 22:28 ` Neil Jerram
2008-12-07 16:51 ` Neil Jerram
2008-01-17 23:13 ` Neil Jerram
2008-01-18 0:30 ` Gregory Marton
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=Pine.LNX.4.62.0801171659460.6868@ashmore.csail.mit.edu \
--to=gremio@mit.edu \
--cc=INVALID.NOREPLY@gnu.org \
--cc=bug-guile@gnu.org \
--cc=neil@ossau.uklinux.net \
/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).