From: ludo@gnu.org (Ludovic Courtès)
To: Christopher Allan Webber <cwebber@dustycloud.org>
Cc: guile-devel@gnu.org
Subject: Re: rename from q to queue
Date: Fri, 15 Apr 2016 10:10:34 +0200 [thread overview]
Message-ID: <874mb3cmx1.fsf@gnu.org> (raw)
In-Reply-To: <874mb4htlj.fsf@dustycloud.org> (Christopher Allan Webber's message of "Thu, 14 Apr 2016 14:35:04 -0500")
Christopher Allan Webber <cwebber@dustycloud.org> skribis:
> Ludovic Courtès writes:
[...]
>> We could do a quick hack to iterate over the exported bindings,
>> re-export them, and print a message.
>>
>> However, I think it would be best to have a mechanism in the module
>> abstraction to /declare/ renames. That would allow both the compiler
>> and the run-time support to emit an appropriate warning.
>>
>> This would require something like adding a special field to ‘module’
>> records, such that one can write, say:
>>
>> (define-module (ice-9 q)
>> #:superseded-by (ice-9 queue))
>>
>> With that in place, it will become much easier to discuss about ice-9
>> renames, IMO.
>>
>> Thoughts?
>>
>> Thanks,
>> Ludo’.
>
> I think that would be useful. There's been talk about renaminig things
> from (ice-9) into a (guile) namespace. Likewise aliasing things from
> (srfi) to something more human-readable. Are the rename and aliasing
> thing the same step or two different things?
Module aliases and deprecation would probably be implemented similarly,
so there’s a connection between the two.
Ludo’.
prev parent reply other threads:[~2016-04-15 8:10 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-11 17:29 rename from q to queue rain1
2016-04-12 3:55 ` Christopher Allan Webber
2016-04-12 4:02 ` Nala Ginrut
2016-04-12 9:41 ` Mathieu Lirzin
2016-04-14 14:15 ` Ludovic Courtès
2016-04-14 19:35 ` Christopher Allan Webber
2016-04-15 8:10 ` Ludovic Courtès [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=874mb3cmx1.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=cwebber@dustycloud.org \
--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).