From: Robin Tarsiger <rtt@dasyatidae.com>
To: emacs-devel@gnu.org
Subject: Re: declare function/macro private
Date: Tue, 8 Jun 2021 12:26:44 -0500 [thread overview]
Message-ID: <15a2ffe9-aac2-f28f-aa5e-4a1c78c460ae@dasyatidae.com> (raw)
In-Reply-To: <87mts0ofmu.fsf@gnus.org>
Lars Ingebrigtsen wrote:
> But... I think I agree with people that this isn't really the way to
> go -- the current convention provides more information than the declare
> would do (most of all, it says what the prefix is).
FWIW, when I saw this thread, what I imagined was something like
(put 'foo--check-baz 'warn-if-used-outside '("foo-")) underneath,
probably with a function for applying that to a lot of symbols at
once. But the lack of a real package system could make that slow
if nothing else---AFAIK obarrays don't do any prefix indexing,
since they're described as hash tables?
-RTT
next prev parent reply other threads:[~2021-06-08 17:26 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-06 4:27 declare function/macro private Paul W. Rankin via Emacs development discussions.
2021-06-06 7:09 ` Omar Polo
2021-06-06 7:18 ` Paul W. Rankin via Emacs development discussions.
2021-06-06 9:53 ` Lars Ingebrigtsen
2021-06-06 12:43 ` Paul W. Rankin via Emacs development discussions.
2021-06-08 9:43 ` Lars Ingebrigtsen
2021-06-08 17:26 ` Robin Tarsiger [this message]
2021-06-06 18:05 ` Stefan Monnier
2021-06-06 18:12 ` Tassilo Horn
2021-06-06 20:12 ` Stefan Monnier
2021-06-07 0:51 ` Paul W. Rankin via Emacs development discussions.
2021-06-07 1:37 ` Arthur Miller
2021-06-07 1:43 ` Paul W. Rankin via Emacs development discussions.
2021-06-07 13:38 ` Arthur Miller
2021-06-07 0:59 ` Paul W. Rankin via Emacs development discussions.
2021-06-07 2:54 ` Stefan Monnier
2021-06-07 18:24 ` Arthur Miller
-- strict thread matches above, loose matches on Subject: below --
2021-06-07 3:35 Boruch Baum
2021-06-07 4:49 ` Paul W. Rankin via Emacs development discussions.
2021-06-07 5:59 ` Stefan Monnier
2021-06-07 6:45 ` Paul W. Rankin via Emacs development discussions.
2021-06-07 12:39 ` Eli Zaretskii
2021-06-08 1:14 ` Boruch Baum
2021-06-08 4:20 ` Arthur Miller
2021-06-08 5:49 ` tomas
2021-06-08 15:46 ` Stefan Monnier
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/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=15a2ffe9-aac2-f28f-aa5e-4a1c78c460ae@dasyatidae.com \
--to=rtt@dasyatidae.com \
--cc=emacs-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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs.git
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).