From: David Kastrup <dak@gnu.org>
To: guile-devel@gnu.org
Subject: Re: Bug in documentation for eq? ?
Date: Wed, 20 Jun 2012 17:25:03 +0200 [thread overview]
Message-ID: <871ulaatv4.fsf@fencepost.gnu.org> (raw)
In-Reply-To: CANY8u7HoKcqHSPCgS08YrNGXQoqa5p4+mSMe_Om8Z=T5MWRU2Q@mail.gmail.com
Pierpaolo Bernardi <olopierpa@gmail.com> writes:
> On Wed, Jun 20, 2012 at 4:27 PM, David Kastrup <dak@gnu.org> wrote:
>> Andy Wingo <wingo@pobox.com> writes:
>>
>> If the Scheme standard states that
>>
>> (and (pair? x) (not (eq? (car x) (car x))))
>>
>> can return #t in a conforming implementation, that means that the
>> standard failed to do its job for weeding out implementations with
>> unusable behavior.
>
> The standard did its job by defining eqv?
>
> Do a (define eq? eqv?) at the start of your programs and you have what
> you are asking for.
Except efficiency. It appears you are confused about what I am asking
for.
I am perfectly fine with the possibility (eq? 0 0) => #f
I am not fine with the possibility (eq? (car x) (car x)) => #f
But it is clear that there is no interest in providing sane invariants
for Guile programmers, so we can just quit this absurdity.
--
David Kastrup
prev parent reply other threads:[~2012-06-20 15:25 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-20 10:40 Bug in documentation for eq? ? David Kastrup
2012-06-20 10:58 ` Andy Wingo
2012-06-20 11:32 ` David Kastrup
2012-06-20 11:47 ` David Kastrup
2012-06-20 13:17 ` Andy Wingo
2012-06-20 13:41 ` Noah Lavine
2012-06-20 14:22 ` Andy Wingo
2012-06-20 14:31 ` David Kastrup
2012-06-20 14:47 ` Andy Wingo
2012-06-20 15:19 ` David Kastrup
2012-06-20 14:27 ` David Kastrup
2012-06-20 14:43 ` Andy Wingo
2012-06-20 15:16 ` David Kastrup
2012-06-20 15:29 ` Andy Wingo
2012-06-20 14:56 ` Pierpaolo Bernardi
2012-06-20 15:25 ` David Kastrup [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=871ulaatv4.fsf@fencepost.gnu.org \
--to=dak@gnu.org \
--cc=guile-devel@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).