From: Tim Landscheidt <tim@tim-landscheidt.de>
To: tpeplt@gmail.com
Cc: help-gnu-emacs@gnu.org, Stefan Monnier <monnier@iro.umontreal.ca>
Subject: Re: Idiomatic way to avoid unused lexical variable in ‘dotimes’ or ‘dolist’?
Date: Wed, 27 Mar 2024 03:52:47 +0000 [thread overview]
Message-ID: <87le648h68.fsf@vagabond.tim-landscheidt.de> (raw)
In-Reply-To: <87msqk8maf.fsf@gmail.com> (tpeplt@gmail.com's message of "Tue, 26 Mar 2024 22:02:16 -0400")
(anonymous) wrote:
>>> 1. Is there an idiom in Emacs Lisp for writing this that
>>> eliminates this warning?
>> (dotimes (_ 100)
>> (insert "I will not obey absurd orders\n"))
>> Or any other var name that starts with an underscore.
> Thank you. I have not been able to find this documented anywhere (that
> is, that lexical variables whose names begin with an underscore are not
> flagged with a warning message if they are not referenced). This
> appears to be true with, for example, ‘let’ expressions, also.
It is mentioned in the GNU Emacs Lisp Reference Manual (C-h
i g (elisp) RET) in the node "Converting to Lexical
Binding":
| […]
| A warning about an unused variable may be a good hint that the
| variable was intended to be dynamically scoped (because it is actually
| used, but in another function), but it may also be an indication that
| the variable is simply really not used and could simply be removed. So
| you need to find out which case it is, and based on that, either add a
| ‘defvar’ or remove the variable altogether. If removal is not possible
| or not desirable (typically because it is a formal argument and that we
| cannot or don’t want to change all the callers), you can also add a
| leading underscore to the variable’s name to indicate to the compiler
| that this is a variable known not to be used.)
| […]
Tim
next prev parent reply other threads:[~2024-03-27 3:52 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-26 22:26 Idiomatic way to avoid unused lexical variable in ‘dotimes’ or ‘dolist’? tpeplt
2024-03-26 22:30 ` Stefan Monnier via Users list for the GNU Emacs text editor
2024-03-27 2:02 ` tpeplt
2024-03-27 3:52 ` Tim Landscheidt [this message]
2024-03-27 5:01 ` tpeplt
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=87le648h68.fsf@vagabond.tim-landscheidt.de \
--to=tim@tim-landscheidt.de \
--cc=help-gnu-emacs@gnu.org \
--cc=monnier@iro.umontreal.ca \
--cc=tpeplt@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.
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).