From: Maxim Cournoyer <maxim.cournoyer@gmail.com>
To: Bruno Victal <mirai@makinata.eu>
Cc: guile-devel@gnu.org,
spk121@yahoo.com,maximedevos@telenet.be,taylan.kammer@gmail.com
Subject: Re: Replacing Guile test-suite with SRFI-64?
Date: Tue, 31 Oct 2023 09:20:43 -0400 [thread overview]
Message-ID: <87ttq7szbo.fsf@gmail.com> (raw)
In-Reply-To: <87h6nlyryy.fsf@makinata.eu> (Bruno Victal's message of "Sat, 23 Sep 2023 13:49:41 +0100")
Hi,
Bruno Victal <mirai@makinata.eu> writes:
> Hi,
>
> Would a rewrite of the Guile tests using SRFI-64 be a welcome idea?
> IMO the advantages of doing so are:
>
> * Less “specifics” that need to be learned solely for working with
> Guile. It's easier for people already using SRFI-64 to “bring in” their
> experience.
>
> * Standardized/portable. Straightforward to integrate external modules
> or SRFI sample implementations into Guile.
>
> * Pre-existing documentation.
I do not have extensive experience with the current test runner used by
Guile itself, but it sounds like a good idea to standardize to use
SRFI-64, as more people already know that library, and many SRFIs
published,
e.g. <https://github.com/scheme-requests-for-implementation/srfi-209/tree/master>,
come with a SRFI-64 test suite, so it'd be less boilerplate to integrate
them.
Also, I like the idea of dogfooding *the* testing library of
Scheme/Guile. If it fails short of the current custom testing framework
used by Guile, we should improve it. This effort will help testing any
Guile/Scheme authored project out there, so is worth it in my opinion.
--
Thanks,
Maxim
prev parent reply other threads:[~2023-10-31 13:20 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-23 12:49 Replacing Guile test-suite with SRFI-64? Bruno Victal
2023-09-23 15:13 ` Mike Gran
2023-09-24 22:27 ` Maxime Devos
2023-09-24 23:32 ` Mike Gran
2023-09-25 9:48 ` Maxime Devos
2023-09-26 8:17 ` Taylan Kammer
2023-09-27 16:12 ` Taylan Kammer
2023-09-26 12:25 ` Bruno Victal
2023-10-31 13:20 ` Maxim Cournoyer [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=87ttq7szbo.fsf@gmail.com \
--to=maxim.cournoyer@gmail.com \
--cc=guile-devel@gnu.org \
--cc=maximedevos@telenet.be \
--cc=mirai@makinata.eu \
--cc=spk121@yahoo.com \
--cc=taylan.kammer@gmail.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).