From: ludo@gnu.org (Ludovic Courtès)
To: guile-devel@gnu.org
Subject: Re: [patch] SRFI-69 support
Date: Mon, 03 Dec 2007 13:40:43 +0100 [thread overview]
Message-ID: <878x4c7xys.fsf@chbouib.org> (raw)
In-Reply-To: 1196541025.25569.40.camel@nocandy.dyndns.org
Hi,
Stephen Compall <s11@member.fsf.org> writes:
> Here is SRFI-69, Basic hash tables, implemented by me from scratch in
> Scheme, including a manual section and a few tests. Patch does not
> include log entries, listed immediately below instead:
Perfect! I committed it to HEAD and 1.8.
Then there's always the question of whether we should `:replace'
`make-hash-table', `hash-table?', etc., as opposed to just exporting it
---I'm for `:replace', but others disagree. ;-)
Thanks,
Ludovic.
_______________________________________________
Guile-devel mailing list
Guile-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/guile-devel
next prev parent reply other threads:[~2007-12-03 12:40 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-12-01 20:30 [patch] SRFI-69 support Stephen Compall
2007-12-01 20:36 ` Stephen Compall
2007-12-03 12:40 ` Ludovic Courtès [this message]
2007-12-05 22:26 ` Andy Wingo
2007-12-06 4:24 ` Stephen Compall
2007-12-09 17:26 ` 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=878x4c7xys.fsf@chbouib.org \
--to=ludo@gnu.org \
--cc=guile-devel@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).