From: Atticus <atticus0@posteo.org>
To: 21855@debbugs.gnu.org
Subject: bug#21855: eq?
Date: Sat, 07 Nov 2015 13:58:48 +0100 [thread overview]
Message-ID: <87r3k2ezjr.fsf@posteo.org> (raw)
So I wanted to try out gnu guix and thus make myself more familiar with
guile first. While running some tests I encountered a problem/bug with eq?:
$ guile -v
guile (GNU Guile) 2.1.1
$ guile
scheme@(guile-user)>
(define (multirember a lat)
(cond
((null? lat) '())
((eq? (car lat) a) (multirember a (cdr lat)))
(else (cons (car lat) (multirember a (cdr lat))))))
scheme@(guile-user)> (multirember '(a b) '(x y (a b) z (a b)))
$1 = (x y z)
So why does guile return (x y z)? I expected (x y (a b) z (a b)). I know
eq? should only be used with symbols (and thus this example is more
theoretical) but nevertheless the return value is not right, since (eq?
'(a b) '(a b)) returns #f (Btw same in guile 2.0.11).
next reply other threads:[~2015-11-07 12:58 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-07 12:58 Atticus [this message]
2015-11-08 10:23 ` bug#21855: eq? tomas
2015-11-08 13:30 ` Atticus
2015-11-08 13:38 ` tomas
2015-11-09 7:57 ` Atticus
2016-06-24 15:31 ` Andy Wingo
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=87r3k2ezjr.fsf@posteo.org \
--to=atticus0@posteo.org \
--cc=21855@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).