From: Rob Browning <rlb@defaultvalue.org>
To: 37461@debbugs.gnu.org
Subject: bug#37461: define-generic doesn't promote equal? to generic
Date: Sat, 21 Sep 2019 12:08:25 -0500 [thread overview]
Message-ID: <87zhix1ss6.fsf@trouble.defaultvalue.org> (raw)
In-Reply-To: <87blvfzx1f.fsf@trouble.defaultvalue.org>
Rob Browning <rlb@defaultvalue.org> writes:
> A re-export doesn't affect the module using the re-exporter, and export
> and replace both fail with "Unbound variable: equal?", even though
> there's a (define equal? ...) in the module.
Perhaps there was something else going on, but now :replace does appear
to work, e.g. if I define a completely new generic and then
(define equal? new-equal)
a "replace: (equal?)" in the define-module does appear to work when you
use the module.
Though define-method still ignores attempts to specialize (or change the
specialization) for existing types like <string>, etc. (as mentioned in
my other message).
Thanks
--
Rob Browning
rlb @defaultvalue.org and @debian.org
GPG as of 2011-07-10 E6A9 DA3C C9FD 1FF8 C676 D2C4 C0F0 39E9 ED1B 597A
GPG as of 2002-11-03 14DD 432F AE39 534D B592 F9A0 25C8 D377 8C7E 73A4
next prev parent reply other threads:[~2019-09-21 17:08 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-19 15:37 bug#37461: define-generic doesn't promote equal? to generic Rob Browning
2019-09-19 23:27 ` Rob Browning
2019-09-21 15:15 ` Rob Browning
2019-09-21 17:08 ` Rob Browning [this message]
2019-09-23 15:01 ` Mikael Djurfeldt
2019-09-28 16:51 ` Mikael Djurfeldt
2019-09-28 17:31 ` 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=87zhix1ss6.fsf@trouble.defaultvalue.org \
--to=rlb@defaultvalue.org \
--cc=37461@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).