From: Taylan Kammer <taylan.kammer@gmail.com>
To: "Aleix Conchillo Flaqué" <aconchillo@gmail.com>
Cc: guile-user <guile-user@gnu.org>
Subject: Re: issues unit testing with srfi-64
Date: Sun, 30 Dec 2018 20:47:47 +0100 [thread overview]
Message-ID: <87wonqu78c.fsf@gmail.com> (raw)
In-Reply-To: <CA+XASoVksnakNnfEmTXKPfnUm7+bWSeL-N4tBS=HtAm4Hkx0HQ@mail.gmail.com> ("Aleix Conchillo \=\?utf-8\?Q\?Flaqu\=C3\=A9\=22's\?\= message of "Sat, 29 Dec 2018 22:03:40 -0800")
FWIW, I have a SRFI-64 implementation whose code-base and default test
runner is somewhat cleaner than the upstream one:
https://github.com/TaylanUB/scheme-srfis/tree/master/srfi/64
(All actual code is in the *.body.scm files. Others are R7RS library
wrappers.)
It sounds like using a custom test runner was the right thing in your
case though, so the default test runner of the implementation is
probably unimportant.
- Taylan
prev parent reply other threads:[~2018-12-30 19:47 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-29 23:50 issues unit testing with srfi-64 Aleix Conchillo Flaqué
2018-12-30 2:17 ` Christopher Lam
2018-12-30 6:03 ` Aleix Conchillo Flaqué
2018-12-30 19:47 ` Taylan Kammer [this message]
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=87wonqu78c.fsf@gmail.com \
--to=taylan.kammer@gmail.com \
--cc=aconchillo@gmail.com \
--cc=guile-user@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).