From: Helmut Eller <eller.helmut@gmail.com>
To: 8711@debbugs.gnu.org
Subject: bug#8711: 24.0.50; binding _ to unused values with lexical-binding
Date: Mon, 23 May 2011 22:16:22 +0200 [thread overview]
Message-ID: <m2ipt1b2ax.fsf@gmail.com> (raw)
In-Reply-To: <m2lixzj3lp.fsf@gmail.com>
* Stefan Monnier [2011-05-23 19:29] writes:
>> My problem is basically that I have a macro "destructure-case" that
>> expands to destructuring-bind, e.g.:
>
>> (destructure-case location
>> ((:error _) nil)) ; do nothing
>
>> expands to
>
>> (ecase (car location)
>> (:error (destructuring-bind (_) (cdr location)
>> (ignore _)
>> nil)))
>
>> The macro inserts the (ignore _) to suppress the "value returned from
>> (car --cl-rest--) is unused" warning.
>
> It can insert (ignore nil) instead which should have the same effect but
> without triggering the other warning with lexical-binding.
Indeed. But I quickly run into another case where that doesn't help:
(defun foo (x) (destructuring-bind (y &rest _) x y))
>> There is also a somewhat related problem with loop:
>
>> ;; -*- lexical-binding: t -*-
>> (defun foo (alist) (loop for (_key . value) in alist collect value))
>
>> produces a "variable `_key' not left unused" warning.
>
> I think the same problem happens with dotimes/dolist using the old
> definition: the loop vars `key' and `value' are let-bound outside the
> loop and then setq'd at each loop iteration (it's this setq that causes
> them to be "not left unused"). This was OK for the dynamic scoping case
> because let-binding is significantly more costly than setq, but it is
> not right for the lexical scoping case where the cost of let is not
> higher than `setq' and where the semantic is actually then wrong:
> e.g. if you "collect (lambda () value)" the current code ends up
> returning a list of functions that all return the last `value', rather
> than a list of functions that each return one of the `values' in
> the alist.
The semantic of loop (in Common Lisp) allows both variants. So the
"portable" idiom is "collect (let ((value value)) (lambda () value))".
Helmut
next prev parent reply other threads:[~2011-05-23 20:16 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-21 18:44 bug#8711: 24.0.50; binding _ to unused values with lexical-binding Helmut Eller
2011-05-23 9:01 ` Lawrence Mitchell
2011-05-23 14:24 ` Stefan Monnier
2011-05-23 18:23 ` Helmut Eller
2011-05-23 19:29 ` Stefan Monnier
2011-05-23 20:16 ` Helmut Eller [this message]
2011-05-24 0:56 ` Stefan Monnier
2011-05-24 6:01 ` Helmut Eller
2011-05-24 12:42 ` Stefan Monnier
2011-06-02 11:17 ` Juanma Barranquero
2011-06-02 12:45 ` Stefan Monnier
2011-06-02 13:41 ` Juanma Barranquero
2011-06-02 14:00 ` Stefan Monnier
2011-06-02 17:10 ` Juanma Barranquero
2011-05-23 20:32 ` Helmut Eller
2011-05-24 0:51 ` Stefan Monnier
2022-05-08 12:33 ` bug#8711: bug#26960: 26.0.50; Complaints about unused variable in cl-destructuring-bind Lars Ingebrigtsen
2022-05-08 13:32 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-05-09 9:25 ` bug#8711: " Lars Ingebrigtsen
2022-05-09 12:26 ` 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
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=m2ipt1b2ax.fsf@gmail.com \
--to=eller.helmut@gmail.com \
--cc=8711@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).