From: Konstantin Kharlamov <Hi-Angel@yandex.ru>
To: Ihor Radchenko <yantar92@posteo.net>
Cc: Michael Heerdegen <michael_heerdegen@web.de>,
Eli Zaretskii <eliz@gnu.org>,
69108@debbugs.gnu.org
Subject: bug#69108: false-positive warning "variable ‘_’ not left unused" in if-let* and if-let
Date: Mon, 19 Feb 2024 16:44:22 +0300 [thread overview]
Message-ID: <508a0205d8a0242ef3385f54722587e99f9a5ffd.camel@yandex.ru> (raw)
In-Reply-To: <87v86keijv.fsf@localhost>
You were right after all 😊 I confirm your findings, thank you for
explanation!
On Mon, 2024-02-19 at 12:37 +0000, Ihor Radchenko wrote:
> Konstantin Kharlamov <Hi-Angel@yandex.ru> writes:
>
> > 6. Evaluate `(benchmark-run-compiled 1 (color-identifiers:elisp-
> > get-declarations))`
>
> This is not enough. You also need to run
> (byte-compile #'color-identifiers:elisp-get-declarations)
>
> With this, I am getting
>
> (0.014252469 0 0.0)
> (0.014183416999999999 0 0.0)
> with pcase
>
> and
>
> (0.014351118 0 0.0)
> (0.014329416 0 0.0)
> with cond
>
> No measurable difference.
>
next prev parent reply other threads:[~2024-02-19 13:44 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-13 21:21 bug#69108: false-positive warning "variable ‘_’ not left unused" in if-let* and if-let Konstantin Kharlamov
2024-02-14 1:01 ` Michael Heerdegen via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-02-17 0:28 ` Michael Heerdegen via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-02-17 8:04 ` Eli Zaretskii
2024-02-17 9:20 ` Konstantin Kharlamov
2024-02-17 11:45 ` Ihor Radchenko
2024-02-17 10:09 ` Konstantin Kharlamov
2024-02-19 12:37 ` Ihor Radchenko
2024-02-19 13:44 ` Konstantin Kharlamov [this message]
2024-02-17 21:46 ` Michael Heerdegen via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-02-17 22:02 ` Michael Heerdegen via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-02-18 6:53 ` Eli Zaretskii
2024-02-25 1:54 ` Michael Heerdegen via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-02-25 7:42 ` Eli Zaretskii
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=508a0205d8a0242ef3385f54722587e99f9a5ffd.camel@yandex.ru \
--to=hi-angel@yandex.ru \
--cc=69108@debbugs.gnu.org \
--cc=eliz@gnu.org \
--cc=michael_heerdegen@web.de \
--cc=yantar92@posteo.net \
/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).