From: "Chris K. Jester-Young" <cky944@gmail.com>
To: guile-devel@gnu.org
Subject: SRFI 41, revisited
Date: Tue, 11 Sep 2012 01:38:35 -0400 [thread overview]
Message-ID: <20120911053835.GA24549@yarrow> (raw)
It's been over half a year since I last wrote about SRFI 41; two whole
releases have happened since then. I'm pretty sure I don't want to wait
for another. ;-)
Thanks to Andy and Ludovic for all the feedback last time; I think I've
implemented all the feedback, so let's get this thing across the finish
line! I just updated the srfi-41 branch with a merge of v2.0.6, and ran
the tests (which passed with no changes to the code).
So, a final review would be highly appreciated.
One thing that is still missing is the documentation. I believe Ludovic
mentioned that this can be lifted straight from the SRFI specification
if need be. (I do hope to write something more original, even if only as
a later thing. But let's not let that hold up making srfi-41 available!)
Cheers,
Chris.
next reply other threads:[~2012-09-11 5:38 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-09-11 5:38 Chris K. Jester-Young [this message]
2012-09-11 5:58 ` SRFI 41, revisited Daniel Hartwig
2012-09-11 6:56 ` Chris K. Jester-Young
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=20120911053835.GA24549@yarrow \
--to=cky944@gmail.com \
--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).