GNU bug report logs - #49407
Request: Specify default values in `map-let` in Map.el

Previous Next

Full log

Message #37 received at 49407 <at> debbugs.gnu.org (full text, mbox):

From: "Basil L. Contovounesios" <contovob <at> tcd.ie>
To: Michael Heerdegen <michael_heerdegen <at> web.de>
Cc: Okam <okamsn <at> protonmail.com>, Lars Ingebrigtsen <larsi <at> gnus.org>,
 49407 <at> debbugs.gnu.org, Nicolas Petton <nicolas <at> petton.fr>,
 Stefan Monnier <monnier <at> iro.umontreal.ca>
Subject: Re: bug#49407: Request: Specify default values in `map-let` in Map.el
Date: Fri, 28 Jul 2023 20:02:08 +0200

Okam via "Bug reports for GNU Emacs, the Swiss army knife of text editors" [2023-07-27 01:39 +0000] wrote:

> From 99208ca640d4944c57082772702cb8534fe91d32 Mon Sep 17 00:00:00 2001
> From: Earl Hyatt <okamsn <at> protonmail.com>

I think your past contributions were under "Earl Hyatt
<ej32u <at> protonmail.com>", right?  Is okamsn <at> protonmail.com your current
address?  Eli, does it make a difference for the CA, do we need to
update .mailmap, or anything like that?

> Date: Thu, 20 Jul 2023 21:44:41 -0400
> Subject: [PATCH v3] Allow default values in 'map-let' and the pcase 'map' form
>
> * lisp/emacs-lisp/map.el (map-let, map)
> (map--make-pcase-bindings): Add a third argument for specifying a
> default value, like in 'map-elt'. (Bug#49407)
>
> * lisp/emacs-lisp/map.el (map--make-pcase-bindings): Clarify that keys
> that aren't found aren't ignored, they actually get the value
> nil (unless the new default value is given). The overall pattern can
                                             ^^
                                             Two spaces here.

[...]

> +Each element in ARGS can be of the form (KEY PAT) or (KEY PAT
> +DEFAULT), where KEY is the key sought in the map, PAT is a
> +`pcase' pattern, and DEFAULT is the default value to use if KEY
> +isn't found.  Both KEY and DEFAULT are evaluated.  If DEFAULT
> +isn't given, then nil is used.

FWIW, the form/structure can be kept on a single line, and a couple of
passive voices avoided, by rewording as e.g.

  Each element of ARGS can be of the form (KEY PAT [DEFAULT]),
  which looks up KEY in the map and matches the associated value
  against `pcase' pattern PAT.  DEFAULT specifies the fallback
  value to use when KEY is not present in the map.  If omitted, it
  defaults to nil.  Both KEY and DEFAULT are evaluated.

> +The match fails if:
> +
> +- KEY is found and PAT does not match the associated value
> +
> +- KEY is not found, DEFAULT is given, and PAT does not match
> +  DEFAULT
> +
> +- KEY is not found, DEFAULT is not given, and PAT does not match
> +  nil"

I find this partly redundant/repetitive, since we already know that PAT
is meant to match either KEY's value (when found), or DEFAULT (which
defaults to nil).

What this doesn't make explicit (compared to the previous version) is
what happens when there are multiple ARGS; specifically, when one or
more of them don't match.

> +KEYS can also be a list of (KEY VARNAME) pairs and
> +\(KEY VARNAME DEFAULT) triples, in which case KEY and

This could also use (KEY VARNAME [DEFAULT]) syntax, if preferred.

Otherwise LGTM, thanks,

-- 
Basil

Previous Next

GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.