From: Mark H Weaver <mhw@netris.org>
To: Zefram <zefram@fysh.org>
Cc: 16362@debbugs.gnu.org, request@debbugs.gnu.org
Subject: bug#16362: compiler disrespects referential integrity
Date: Wed, 01 Oct 2014 15:04:00 -0400 [thread overview]
Message-ID: <878ukz8vdr.fsf@yeeloong.lan> (raw)
In-Reply-To: <20140116015744.GA21945@fysh.org> (zefram@fysh.org's message of "Thu, 16 Jan 2014 01:57:44 +0000")
tags 16362 + notabug wontfix
close 16362
thanks
I'm sorry that you came to depend on the undocumented behavior of
earlier versions of Guile, but the Scheme standards are quite clear that
literals are immutable and that no guarantees are made about preserving
object identity as seen by eq? or eqv?. To my knowledge we never made
any promises that this would work, and we can't make it work properly in
the general case in our new ahead-of-time compilation model.
I'm closing this ticket.
Mark
prev parent reply other threads:[~2014-10-01 19:04 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-05 23:13 bug#16362: compiler disrespects referential integrity Zefram
2014-01-15 19:57 ` Mark H Weaver
2014-01-15 21:02 ` Zefram
2014-01-15 22:15 ` Mark H Weaver
2014-01-16 1:57 ` Zefram
2014-10-01 19:04 ` Mark H Weaver [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=878ukz8vdr.fsf@yeeloong.lan \
--to=mhw@netris.org \
--cc=16362@debbugs.gnu.org \
--cc=request@debbugs.gnu.org \
--cc=zefram@fysh.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).