From: "Sjoerd van Leent Privé" <svanleent@gmail.com>
To: Ian Price <ianprice90@googlemail.com>
Cc: guile-devel@gnu.org
Subject: Re: Immutable rnrs hashtable
Date: Mon, 26 Nov 2012 10:44:41 +0100 [thread overview]
Message-ID: <50B33A09.7090303@gmail.com> (raw)
In-Reply-To: <87mwy5b1ej.fsf@Kagami.home>
Hi Ian,
The implementation is okay, I wrote a half baked example, as I
understood the bit to be the mutable field. But it should act in
reverse. Got it. In many cases, I use info-lookup-symbol in Guile's
documentation, as it is much easier to navigate than the RNRS website
(which I consider bad design, as there is no sensible hierarchy
whatsoever or something of a decent index).
This is why I got it wrong, as the documentation was mistaken, and I did
the opposite of what I should be doing. And yes, I was using #t and #f,
But I expected the results to be the other way around.
Btw, isn't their a hashtable which is more pure in it's implementation?
The RNRS and SRFI-69 versions are having quite some side-effects. I
would have expected a method like "hashtable-add" which copies an
existing hashtable, adds values and returns a new hashtable. I know, I
prefer pure functional implementations...
Sjoerd
On 11/26/2012 02:25 AM, Ian Price wrote:
> Whoops, in my haste, I forgot to note that this _is_ a bug in guile's
> documentation, not in the implementation. Suggested fix included.
>
> Ludovic, Andy:
> Should I add him to THANKS too?
>
next prev parent reply other threads:[~2012-11-26 9:44 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-11-25 23:00 Immutable rnrs hashtable Sjoerd van Leent Privé
2012-11-26 1:07 ` Ian Price
2012-11-26 1:25 ` Ian Price
2012-11-26 9:44 ` Sjoerd van Leent Privé [this message]
2012-11-26 10:28 ` Ian Price
2012-11-26 14:18 ` Sjoerd van Leent Privé
2012-11-26 16:34 ` Ludovic Courtès
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=50B33A09.7090303@gmail.com \
--to=svanleent@gmail.com \
--cc=guile-devel@gnu.org \
--cc=ianprice90@googlemail.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).