From: Michael Heerdegen <michael_heerdegen@web.de>
To: 61730@debbugs.gnu.org
Subject: bug#61730: 30.0.50; Compiler warnings for delq and delete
Date: Thu, 23 Feb 2023 11:29:25 +0100 [thread overview]
Message-ID: <87ilfsisje.fsf@web.de> (raw)
Hello,
I think we should add compiler warnings for `delete' and `delq' function
calls whose return values are unused. Those are most likely unintended:
still some programmers don't know that the return value must be assigned
back because the destructive operation on the original list structure
does not necessarily lead to the return value. It's a pitfall and can
lead to bugs that are hard to debug, so having warnings would be an
improvement.
I think the warnings could be added in a similar way as the "mapcar
called for effect" warnings work.
Adding the same kind of warning for `remq' and `remove' would probably
also be useful. This will probably not occur that often but it still
would be useful I think.
TIA,
Michael.
next reply other threads:[~2023-02-23 10:29 UTC|newest]
Thread overview: 38+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-23 10:29 Michael Heerdegen [this message]
2023-02-24 3:59 ` bug#61730: 30.0.50; Compiler warnings for delq and delete Richard Stallman
2023-02-24 13:43 ` Mattias Engdegård
2023-02-24 13:56 ` Eli Zaretskii
2023-02-24 15:11 ` Michael Heerdegen
2023-02-24 15:29 ` Eli Zaretskii
2023-02-24 15:45 ` Michael Heerdegen
2023-02-24 15:48 ` Eli Zaretskii
2023-02-24 16:17 ` Michael Heerdegen
2023-02-24 16:45 ` Michael Heerdegen
2023-02-24 19:33 ` Mattias Engdegård
2023-02-24 20:20 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-02-25 9:40 ` Mattias Engdegård
2023-02-25 4:15 ` Richard Stallman
2023-02-25 8:11 ` Eli Zaretskii
2023-02-25 12:34 ` Michael Heerdegen
2023-02-25 13:25 ` Eli Zaretskii
2023-02-25 15:09 ` Michael Heerdegen
2023-02-25 15:29 ` Michael Heerdegen
2023-02-25 15:48 ` Eli Zaretskii
2023-02-27 3:22 ` Richard Stallman
2023-02-27 10:37 ` Michael Heerdegen
2023-02-27 11:37 ` Eli Zaretskii
2023-02-27 3:24 ` Richard Stallman
2023-02-27 11:44 ` Eli Zaretskii
2023-02-24 15:52 ` Mattias Engdegård
2023-02-24 16:37 ` Michael Heerdegen
2023-04-09 16:41 ` Mattias Engdegård
2023-05-01 16:06 ` Mattias Engdegård
2023-05-20 1:57 ` Michael Heerdegen
2023-05-20 9:14 ` Mattias Engdegård
2023-05-21 0:56 ` Michael Heerdegen
2023-05-21 3:01 ` Ruijie Yu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-05-21 3:57 ` Michael Heerdegen
2023-05-21 5:55 ` Eli Zaretskii
2023-05-21 8:42 ` Mattias Engdegård
2023-05-31 14:38 ` Mattias Engdegård
2023-06-01 0:48 ` Michael Heerdegen
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=87ilfsisje.fsf@web.de \
--to=michael_heerdegen@web.de \
--cc=61730@debbugs.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).