From: Erik Dominikus <erik.dominikus71@gmail.com>
To: 43304@debbugs.gnu.org
Subject: bug#43304: (scheme base) "member" should return #f if object is not in list
Date: Thu, 10 Sep 2020 10:46:58 +0700 [thread overview]
Message-ID: <CAOopUjn+rhmpCdbFsP7b3228Boz=1GTQ2RHSmXo1Twk=n_Nucg@mail.gmail.com> (raw)
Dear Guile authors,
I would like to report an issue:
Version: Guile 3.0.2 (but should also apply to master; Git says the
"member" in module/scheme/base.scm hasn't changed since October 2019)
How to reproduce: Run "guile" and then type this:
((@ (scheme base) member) 0 '(1))
Expected: #f
Actual: ()
Reason: page 43 of R7RS-small https://small.r7rs.org/attachment/r7rs.pdf
"If obj does not occur in list, then #f (not the empty list) is returned."
Thank you.
Best regards,
Erik
next reply other threads:[~2020-09-10 3:46 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-10 3:46 Erik Dominikus [this message]
2021-05-12 20:14 ` bug#43304: (scheme base) "member" should return #f if object is not in list Taylan Kammer
2021-05-12 20:15 ` Taylan Kammer
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='CAOopUjn+rhmpCdbFsP7b3228Boz=1GTQ2RHSmXo1Twk=n_Nucg@mail.gmail.com' \
--to=erik.dominikus71@gmail.com \
--cc=43304@debbugs.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).