From: Mark H Weaver <mhw@netris.org>
To: Daniel Hartwig <mandyke@gmail.com>
Cc: "Ludovic Courtès" <ludo@gnu.org>, 13741@debbugs.gnu.org
Subject: bug#13741: guile-2.0: optimize, and eq-ness of literals (test-suite)
Date: Fri, 01 Mar 2013 11:13:17 -0500 [thread overview]
Message-ID: <877glrumhu.fsf@tines.lan> (raw)
In-Reply-To: <CAN3veRfwDxhHTN_SxkWxE51SWzKb+650kMO4QXDhM+=E0EvjtQ@mail.gmail.com> (Daniel Hartwig's message of "Mon, 18 Feb 2013 18:02:15 +0800")
Daniel Hartwig <mandyke@gmail.com> writes:
> On 18 February 2013 17:16, Ludovic Courtès <ludo@gnu.org> wrote:
>> Quoth R5RS:
>>
>> `Eq?''s behavior on numbers and characters is
>> implementation-dependent, but it will always return either true or
>> false, and will return true only when `eqv?' would also return
>> true. `Eq?' may also behave differently from `eqv?' on empty
>> vectors and empty strings.
>>
>> What we may get wrong is that it looks as if it doesn’t always return
>> either true or false, because the behavior depends on whether one of the
>> operands is a literal.
>
> I took that to mean only that eq? always returns a boolean, rather
> than requiring it to return the same boolean given the same numeric
> arguments. It would be fine to simplify some rationals and not
> others, as this action does not affect the outcome of eqv?.
Yes, this is my understanding as well.
Mark
next prev parent reply other threads:[~2013-03-01 16:13 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-18 3:27 bug#13741: guile-2.0: optimize, and eq-ness of literals (test-suite) Daniel Hartwig
2013-02-18 9:16 ` Ludovic Courtès
2013-02-18 10:02 ` Daniel Hartwig
2013-03-01 16:13 ` Mark H Weaver [this message]
2013-02-18 17:19 ` Andy Wingo
2013-02-18 23:48 ` Mark H Weaver
2013-02-19 1:55 ` bug#13741: [PATCH] test-suite: eq-ness of numbers, characters is unspecified Daniel Hartwig
2013-02-19 4:29 ` Daniel Hartwig
2013-02-19 5:19 ` Mark H Weaver
2013-03-01 16:10 ` Mark H Weaver
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=877glrumhu.fsf@tines.lan \
--to=mhw@netris.org \
--cc=13741@debbugs.gnu.org \
--cc=ludo@gnu.org \
--cc=mandyke@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).