From: Marius Vollmer <mvo@zagadka.de>
Cc: guile-devel@gnu.org
Subject: Re: New module system option :duplicates
Date: 07 Mar 2003 16:28:54 +0100 [thread overview]
Message-ID: <87el5jb3gp.fsf@zagadka.ping.de> (raw)
In-Reply-To: <xy71y1jp63y.fsf@nada.kth.se>
Mikael Djurfeldt <djurfeldt@nada.kth.se> writes:
> Marius Vollmer <mvo@zagadka.de> writes:
>
> > Just giving the license to merge any and all generics that have
> > colliding names is probably not what one wants.
>
> Actually, I'd like to have the option to do exactly that. In my view,
> we can reasonably safely regard the merging as an administrative
> non-issue for most programs.
I see, yes. Unasked merging of generics has usually very few if any
negative consequences.
But still, you can not really savely use a generic that has been
merged from two generics without your explicit consent.
The typical situation would be that one part of a module intents to
use the one generic, while another part (written later or by a
different person) intents to use a second generic that happens to have
the same name. The second part will likely add another ":use-module"
clause and ":duplicates merge-generics" will silently merge the two
generics.
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.
I guess it is next to impossible to automatically check whether
overlapping type signatures can be merged the Right Way.
--
GPG: D5D4E405 - 2F9B BCCC 8527 692A 04E3 331E FAF8 226A D5D4 E405
_______________________________________________
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 15:28 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 [this message]
2003-03-07 16:56 ` Rob Browning
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=87el5jb3gp.fsf@zagadka.ping.de \
--to=mvo@zagadka.de \
--cc=guile-devel@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).