From: Rob Browning <rlb@defaultvalue.org>
Cc: djurfeldt@nada.kth.se
Subject: Re: New module system option :duplicates
Date: Fri, 07 Mar 2003 10:56:23 -0600 [thread overview]
Message-ID: <87zno7w1xk.fsf@raven.i.defaultvalue.org> (raw)
In-Reply-To: <87el5jb3gp.fsf@zagadka.ping.de> (Marius Vollmer's message of "07 Mar 2003 16:28:54 +0100")
Marius Vollmer <mvo@zagadka.de> writes:
> When the two generics have non-overlapping type signatures for their
> signatures, all is well. But you can't be sure about this. You
> need to be made aware that there is a collision/merging going on and
> then you can declare that this specific merge is OK.
That's what I just thought about too. i.e. I'd guess that merging
(open <file>) and (open <gripper>) would be just fine, but what about
merging (open <file>) from module-1 with (open <file>) from module-2?
Personally, I'd probably want to see an error in the latter case, but
the question is in general, how would a "conflict" be defined?
--
Rob Browning
rlb @defaultvalue.org, @linuxdevel.com, and @debian.org
Previously @cs.utexas.edu
GPG starting 2002-11-03 = 14DD 432F AE39 534D B592 F9A0 25C8 D377 8C7E 73A4
_______________________________________________
Guile-devel mailing list
Guile-devel@gnu.org
http://mail.gnu.org/mailman/listinfo/guile-devel
next prev parent reply other threads:[~2003-03-07 16:56 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-03-07 13:19 New module system option :duplicates Mikael Djurfeldt
2003-03-07 14:28 ` tomas
2003-03-07 14:49 ` Marius Vollmer
2003-03-07 15:08 ` Mikael Djurfeldt
2003-03-07 15:28 ` Marius Vollmer
2003-03-07 16:56 ` Rob Browning [this message]
2003-03-08 14:38 ` Greg Troxel
2003-03-10 23:39 ` Mikael Djurfeldt
2003-03-11 12:12 ` Mikael Djurfeldt
2003-03-11 12:21 ` Mikael Djurfeldt
2003-03-11 14:29 ` Greg Troxel
2003-03-11 14:47 ` Mikael Djurfeldt
2003-03-10 23:18 ` Mikael Djurfeldt
2003-03-12 15:05 ` Marius Vollmer
2003-03-12 15:18 ` Mikael Djurfeldt
2003-03-12 16:34 ` Marius Vollmer
2003-03-07 16:30 ` Rob Browning
2003-03-10 23:38 ` Mikael Djurfeldt
2003-03-11 0:14 ` Rob Browning
2003-03-11 10:32 ` Mikael Djurfeldt
2003-03-11 10:50 ` Mikael Djurfeldt
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=87zno7w1xk.fsf@raven.i.defaultvalue.org \
--to=rlb@defaultvalue.org \
--cc=djurfeldt@nada.kth.se \
/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).