From: Taylan Kammer <taylan.kammer@gmail.com>
To: guile-user@gnu.org
Subject: Re: srfi-64 tests passing when they should not
Date: Wed, 5 May 2021 08:39:12 +0200 [thread overview]
Message-ID: <0d18f3f4-055f-4371-8e52-6b0ca7d879dd@gmail.com> (raw)
In-Reply-To: <40a496bb-c005-3c6f-2bf2-7025f3a234bb@posteo.de>
On 04.05.2021 10:31, Zelphir Kaltstahl wrote:
>
> The first 2 tests are surprisingly passing. This is also the reason, why I used
> test-assert and manually wrote the (equal? ...) in the last test, to see,
> whether it makes any difference. Indeed it does.
>
The reference implementation of SRFI-64 (which is what Guile ships)
doesn't seem to be written very well.
I have an alternative implementation here, if you're interested:
https://github.com/TaylanUB/scheme-srfis
I'm not sure if the newest Guile is able to run it out of the box
though. You might have to create some .scm symlinks to the .sld files.
- Taylan
next prev parent reply other threads:[~2021-05-05 6:39 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-04 8:31 srfi-64 tests passing when they should not Zelphir Kaltstahl
2021-05-04 10:15 ` Jérémy Korwin-Zmijowski
2021-05-04 11:36 ` Zelphir Kaltstahl
2021-05-05 6:39 ` Taylan Kammer [this message]
2021-05-05 13:47 ` Luis Felipe
2021-05-06 11:16 ` Taylan Kammer
2021-05-06 15:33 ` Luis Felipe
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=0d18f3f4-055f-4371-8e52-6b0ca7d879dd@gmail.com \
--to=taylan.kammer@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).