From: Taylan Kammer <taylan.kammer@gmail.com>
To: dsmich@roadrunner.com,
'Arvydas Silanskas' <nma.arvydas.silanskas@gmail.com>
Cc: "'48765-done@debbugs.gnu.org'" <48765@debbugs.gnu.org>
Subject: bug#48765: `member` from (scheme base) returns empty list instead of #f when item is not found
Date: Tue, 1 Jun 2021 02:49:36 +0200 [thread overview]
Message-ID: <3707add2-41a6-ef5a-ceab-5f5559ed0542@gmail.com> (raw)
In-Reply-To: <a66120c5517b510b34919ce1af2d44db2f7e8145@webmail>
On 31.05.2021 23:44, dsmich@roadrunner.com wrote:
> In git main it appears to work but with a warning:
>
> $ guile --r7rs
> GNU Guile 3.0.7.13-c1fd55-dirty
> ...
>
> scheme@(guile-user)> (import (scheme base))
> scheme@(guile-user)> (member 'a '(b))
> WARNING: (guile-user): imported module (scheme base) overrides core binding `member'
> $1 = #f
> scheme@(guile-user)> (member 'a '(b a))
> $2 = (a)
>
>
> -Dale
>
>
> -----------------------------------------
>
> From: "Arvydas Silanskas"
> To: 48765@debbugs.gnu.org
> Cc:
> Sent: Monday May 31 2021 5:10:12PM
> Subject: bug#48765: `member` from (scheme base) returns empty list instead of #f when item is not found
>
> Default `member` works fine:
>
> $ guile
>> (member 'a '(b)) $1 = #f
>
> However, using scheme base it returns empty list
> $ guile --r7rs
>> (import (scheme base))
>> (member 'a '(b))
> $1 = ()
> Other functions (memq, memv) seem to work fine.
> I am using version 3.0.5 as distributed by debian bullseye
The fix for this was part of the 3.0.6 release. :-)
Older report on the same bug:
https://bugs.gnu.org/43304
The warning can be safely ignored, and I believe it won't appear
when writing an R7RS library using 'define-library'.
Closing this report but feel free to ask further questions.
--
Taylan
next prev parent reply other threads:[~2021-06-01 0:49 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-31 21:07 bug#48765: `member` from (scheme base) returns empty list instead of #f when item is not found Arvydas Silanskas
2021-05-31 21:44 ` dsmich
2021-06-01 0:49 ` Taylan Kammer [this message]
2021-07-16 2:22 ` Rob Browning
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=3707add2-41a6-ef5a-ceab-5f5559ed0542@gmail.com \
--to=taylan.kammer@gmail.com \
--cc=48765@debbugs.gnu.org \
--cc=dsmich@roadrunner.com \
--cc=nma.arvydas.silanskas@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).