unofficial mirror of guile-devel@gnu.org 
 help / color / mirror / Atom feed
From: Mikael Djurfeldt <mikael@djurfeldt.com>
To: Mark H Weaver <mhw@netris.org>
Cc: guile-devel <guile-devel@gnu.org>
Subject: Re: Proposal for a new (ice-9 history)
Date: Fri, 2 Nov 2018 15:02:50 +0100	[thread overview]
Message-ID: <CAA2XvwJAzhiOSNZCiEVa7Y_0=UR1yjsyoavOkwvtaDDUMp0Kjg@mail.gmail.com> (raw)
In-Reply-To: <CAA2XvwKLoaL3FcT2ze9MCT8aWhS361BCcg=Yh=JH=_HtMWJ0Bg@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 1458 bytes --]

On Fri, Nov 2, 2018 at 2:35 PM Mikael Djurfeldt <mikael@djurfeldt.com>
wrote:

> Given this situation, is there still a way to use the module system to
> give (ice-9 match) $ precedence? There is. Göran Weinholt has pointed out
> that other Scheme implementations tend to export their auxilliary keywords.
> If we export $ like this:
>
> --8<---------------cut here---------------start------------->8---
> (define-module (ice-9 match)
>   #:export (match
>                [...]
>
              match-letrec)
>   #:replace ($))
> [...]
> --8<---------------cut here---------------start------------->8---
>
> then (ice-9 match) will gracefully replace $ in (value-history) and match
> will work as expected. A good idea would be to define *all* auxilliary
> keywords to `misplaced' above, according to what Göran has said. That is
> independent of the issue of name collisions.
>

Just to avoid misunderstanding. Of course, to avoid the hard-to-find bugs
which Göran talked about, auxilliary keywords should be exported the normal
way (through export). That way name collisions will be reported. Possibly
that is what we should do here as well, also for $, such that there is a
warning when (ice-9 match) is imported.

Also, what we really wanted to say is not that (ice-9 match) $ is
"replacing". We rather wanted to say that (value-history) $ is "deferring",
but there is no way to do that in the module system right now.

[-- Attachment #2: Type: text/html, Size: 2167 bytes --]

      reply	other threads:[~2018-11-02 14:02 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-10-29 14:13 Proposal for a new (ice-9 history) Mikael Djurfeldt
2018-10-29 23:54 ` Mark H Weaver
2018-10-30  0:55   ` Mikael Djurfeldt
2018-10-30 10:21     ` REPL and load deifferences (was Re: Proposal for a new (ice-9 history)) Mikael Djurfeldt
2018-10-30 12:20       ` Mikael Djurfeldt
2018-10-30 18:01         ` Göran Weinholt
2018-10-30  0:25 ` Proposal for a new (ice-9 history) Mark H Weaver
2018-10-30  1:08   ` Mikael Djurfeldt
2018-10-30  6:20     ` Mark H Weaver
2018-10-30 13:59       ` Mikael Djurfeldt
2018-10-31 16:49         ` Mikael Djurfeldt
2018-11-02 13:35           ` Mikael Djurfeldt
2018-11-02 14:02             ` Mikael Djurfeldt [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='CAA2XvwJAzhiOSNZCiEVa7Y_0=UR1yjsyoavOkwvtaDDUMp0Kjg@mail.gmail.com' \
    --to=mikael@djurfeldt.com \
    --cc=guile-devel@gnu.org \
    --cc=mhw@netris.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).