From: David Pirotte <david@altosw.be>
To: Andrew Erlanger <andrew.erlanger@gmail.com>
Cc: 28837@debbugs.gnu.org
Subject: bug#28837: Guile 2.2.2: Loading srfi-1 with merge-generics breaks "map"
Date: Mon, 16 Oct 2017 23:11:47 -0200 [thread overview]
Message-ID: <20171016231147.10d67570@capac> (raw)
In-Reply-To: <871sm5d4di.fsf@ateguix.i-did-not-set--mail-host-address--so-tickle-me>
[-- Attachment #1: Type: text/plain, Size: 524 bytes --]
Hi Andrew,
> (define-module (mytest f)
> #:use-module (oop goops)
> #:use-module (srfi srfi-1)
> #:duplicates (merge-generics))
You need at least
#:duplicates (merge-generics
replace)
but as I recommended in an earlier message, you should extend the default set
#:duplicates (merge-generics
replace
warn-override-core
warn
last)
> ,in (mytest f) map
> While executing meta-command:
> ERROR: Unbound variable: map
The above will fix your problem.
David
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
prev parent reply other threads:[~2017-10-17 1:11 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-14 17:30 bug#28837: Guile 2.2.2: Loading srfi-1 with merge-generics breaks "map" Andrew Erlanger
2017-10-17 1:11 ` David Pirotte [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=20171016231147.10d67570@capac \
--to=david@altosw.be \
--cc=28837@debbugs.gnu.org \
--cc=andrew.erlanger@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).