GNU bug report logs -
#25929
25.2; map-delete doesn't delete permanently 1st alist elt
Previous Next
Reported by: Tino Calancha <tino.calancha <at> gmail.com>
Date: Thu, 2 Mar 2017 07:19:01 UTC
Severity: normal
Found in version 25.2
Fixed in version 29.1
Done: Lars Ingebrigtsen <larsi <at> gnus.org>
Bug is archived. No further changes may be made.
Full log
Message #53 received at 25929 <at> debbugs.gnu.org (full text, mbox):
Michael Heerdegen <michael_heerdegen <at> web.de> writes:
> Stefan Monnier <monnier <at> iro.umontreal.ca> writes:
>
>> > (macroexp-let2 nil key
>> > `(progn
>> > (map--dispatch ,map
>> > :list (setf (alist-get ,key ,map nil t) nil)
>> > :hash-table (remhash ,key ,map)
>> > :array (and (>= ,key 0)
>> > (<= ,key (seq-length ,map))
>> > (aset ,map ,key nil)))
>> > ,map)))
>>
>> Note that this will make it pretty much impossible to use
>> cl-generic dispatch.
>
> It will also break cases where MAP is an expression that is not a
> symbol:
>
> #+begin_src emacs-lisp
> (let ((thing (cons 'tag (list (cons 0 1) (cons 2 3)))))
> (map-delete (cdr thing) 0))
> ==> nil
>
> (map-delete (list (cons 0 1) (cons 2 3)) 0)
> ==> if: Symbol's function definition is void: \(setf\ list\)
> #+end_src
If MAP isn't a symbol, then map-delete could avoid doing the setf,
couldn't it?
I think that should make for a pretty useful form. You can both say
...
(map-delete foo 'bar)
...
and
(setq foo (cons (map-delete (get-a-list) 'bar) 'zot))
and not be surprised at the results. It's certainly more fun than the
current (setq foo (delete 'bar foo)) we have all over the place, even if
it's something of a departure from how functions like this has
traditionally worked in various Lisps.
--
(domestic pets only, the antidote for overdose, milk.)
bloggy blog: http://lars.ingebrigtsen.no
This bug report was last modified 3 years and 27 days ago.
Previous Next
GNU bug tracking system
Copyright (C) 1999 Darren O. Benham,
1997,2003 nCipher Corporation Ltd,
1994-97 Ian Jackson.