From: Noam Postavsky <npostavs@users.sourceforge.net>
To: John Williams <jrw@pobox.com>
Cc: 26486@debbugs.gnu.org
Subject: bug#26486: 25.1.91; spurious warnings from cconv.el
Date: Thu, 13 Apr 2017 15:28:21 -0400 [thread overview]
Message-ID: <CAM-tV-8QzyxZ4vF5Xv6BkGtXFZX4QjFLxrh-RptcY5TgLKKFTQ@mail.gmail.com> (raw)
In-Reply-To: <CAEdRJLDnJ7Am0S+1xBdjTED50zs8c6Q3oZKdsiwO0He87Vazng@mail.gmail.com>
retitle 26486 25.1.91; unused var warning from cconv.el can't be suppressed
severity 26486 minor
tag 26486 confirmed
quit
On Thu, Apr 13, 2017 at 2:59 PM, John Williams <jrw@pobox.com> wrote:
> When I byte compile a file where a macro expansion introduces an unused
> lexical veriable, I get warnings from cconv.el, even if I wrap the
> expansion in (with-no-warnings) and set byte-compile-warnings to nil.
> IMHO warnings of this type should never be issued for code that comes
> from a macro expansion, but it should at least be possible to suppress
> them with the usual mechanisms. Here's a file that demonstrates the
> problem when it's compiled with byte-compile-file:
>
> ========================================================================
> ;; -*- lexical-binding: t; byte-compile-warnings: nil -*-
>
> (defmacro test ()
> `(let (unused)))
>
> (with-no-warnings
> (test))
> ========================================================================
This happens also without a macro.
;; -*- lexical-binding: t; byte-compile-warnings: nil -*-
(with-no-warnings (let (unused)))
next prev parent reply other threads:[~2017-04-13 19:28 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-13 18:59 bug#26486: 25.1.91; spurious warnings from cconv.el John Williams
2017-04-13 19:28 ` Noam Postavsky [this message]
2021-07-05 15:17 ` bug#26486: 25.1.91; unused var warning from cconv.el can't be suppressed Lars Ingebrigtsen
2021-07-05 15:29 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2021-07-06 14:48 ` Lars Ingebrigtsen
2021-07-06 19:53 ` Basil L. Contovounesios
2021-07-06 20:03 ` Lars Ingebrigtsen
2021-07-06 20:04 ` Lars Ingebrigtsen
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=CAM-tV-8QzyxZ4vF5Xv6BkGtXFZX4QjFLxrh-RptcY5TgLKKFTQ@mail.gmail.com \
--to=npostavs@users.sourceforge.net \
--cc=26486@debbugs.gnu.org \
--cc=jrw@pobox.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 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).