From: Lars Ingebrigtsen <larsi@gnus.org>
To: Phil Sainty <psainty@orcon.net.nz>
Cc: Stefan Kangas <stefankangas@gmail.com>, 58513@debbugs.gnu.org
Subject: bug#58513: describe-function should say that defconst variables are constant
Date: Fri, 14 Oct 2022 14:40:27 +0200 [thread overview]
Message-ID: <87v8om8tok.fsf@gnus.org> (raw)
In-Reply-To: <8fae3292e6c1b175853b557060d05487@webmail.orcon.net.nz> (Phil Sainty's message of "Sat, 15 Oct 2022 01:35:41 +1300")
Phil Sainty <psainty@orcon.net.nz> writes:
> It does at least one thing different: if you load or eval a defconst
> for a variable which already exists, the value is updated.
Yes, that's true.
And we could start adding a symbol property saying that a constant is
meant to be constant, and perhaps start warning if people change it, but
that would make things slower for basic things like `setq', so I'm
pretty sure it's not worth it.
We could use that property to make describe-function say that the
variable isn't meant to be changed, though. But is it worth adding to
the symbol plist just for that? Hm...
next prev parent reply other threads:[~2022-10-14 12:40 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-14 12:04 bug#58513: describe-function should say that defconst variables are constant Stefan Kangas
2022-10-14 12:23 ` Lars Ingebrigtsen
2022-10-14 12:35 ` Phil Sainty
2022-10-14 12:40 ` Lars Ingebrigtsen [this message]
2022-10-14 13:03 ` Stefan Kangas
2022-10-14 13:07 ` Lars Ingebrigtsen
2022-10-14 13:34 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-10-14 14:25 ` Lars Ingebrigtsen
2022-10-14 16:44 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-10-15 10:04 ` Lars Ingebrigtsen
2022-10-16 20:51 ` Richard Stallman
2022-10-16 21:11 ` Drew Adams
2022-10-17 5:41 ` Stefan Kangas
2022-10-17 10:41 ` Lars Ingebrigtsen
2022-10-15 12:33 ` Stefan Kangas
2022-10-15 14:11 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87v8om8tok.fsf@gnus.org \
--to=larsi@gnus.org \
--cc=58513@debbugs.gnu.org \
--cc=psainty@orcon.net.nz \
--cc=stefankangas@gmail.com \
/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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.