From: Drew Adams <drew.adams@oracle.com>
To: Dmitry Gutov <dgutov@yandex.ru>, Lars Ingebrigtsen <larsi@gnus.org>
Cc: "emacs-devel@gnu.org" <emacs-devel@gnu.org>
Subject: RE: [External] : Re: Improve `replace-regexp-in-string' ergonomics?
Date: Wed, 22 Sep 2021 23:24:36 +0000 [thread overview]
Message-ID: <SJ0PR10MB548864DD9DF93CDDBB7A48B7F3A29@SJ0PR10MB5488.namprd10.prod.outlook.com> (raw)
In-Reply-To: <2675d5ef-946d-0474-ef9d-a8989289c3d0@yandex.ru>
> Probably check that the number of &rest arguments divides by two as
> well. Or three, or four?
Giant apologies for not following this thread,
especially if this comment makes no sense in
context.
___
My comment is that &rest is best used for an
_arbitrary_ set (list) of unknown length and
_unknown structure_. Among other things,
that allows for adding more, possibly
unrelated args later.
If instead you hard-code in the body an
expectation that the "rest" of the args will
be of a certain kind, in a certain order, or
in a certain kind of sequence (e.g. mod 2,
mod 3, with given meanings to each of the
pair or triplet items), then you lose this
property of &rest - which is an integral
part of its raison d'etre, IMO.
If you know the structure you want, and you
just want to allow it to have indeterminate
length, then use a single list arg (required
or optional), and specify in the doc string,
and control in the body, the actual form of
the list elements (e.g. triplets of a given
form).
Abusing &rest the way I think you might be
suggesting will ultimately bite you. And
the more you do it, the more it will bite
you elsewhere. Users won't know what to
expect, or they'll have unreasonable
expectations.
Just one opinion. Again, sorry if not on
the real topic.
next prev parent reply other threads:[~2021-09-22 23:24 UTC|newest]
Thread overview: 41+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-22 4:36 Improve `replace-regexp-in-string' ergonomics? Lars Ingebrigtsen
2021-09-22 5:22 ` Yuri Khan
2021-09-22 6:36 ` Lars Ingebrigtsen
2021-09-22 7:47 ` Thierry Volpiatto
2021-09-22 5:24 ` Po Lu
2021-09-22 6:37 ` Lars Ingebrigtsen
2021-09-22 10:56 ` Po Lu
2021-09-22 20:08 ` Lars Ingebrigtsen
2021-09-23 0:11 ` Po Lu
2021-09-22 7:33 ` Adam Porter
2021-09-22 8:09 ` Lars Ingebrigtsen
2021-09-22 7:51 ` Andreas Schwab
2021-09-22 8:14 ` Augusto Stoffel
2021-09-22 8:21 ` Adam Porter
2021-09-22 18:01 ` Stefan Monnier
2021-09-22 18:24 ` Basil L. Contovounesios
2021-09-22 22:56 ` Adam Porter
2021-09-22 23:53 ` Eric Abrahamsen
2021-09-22 20:06 ` Lars Ingebrigtsen
2021-09-22 10:59 ` Dmitry Gutov
2021-09-22 20:18 ` Lars Ingebrigtsen
2021-09-22 22:23 ` Dmitry Gutov
2021-09-22 23:24 ` Drew Adams [this message]
2021-09-22 18:14 ` Stefan Monnier
2021-09-22 19:30 ` Mattias Engdegård
2021-09-22 20:22 ` Lars Ingebrigtsen
2021-09-22 20:29 ` Lars Ingebrigtsen
2021-09-23 2:15 ` Stefan Monnier
2021-10-05 16:18 ` Juri Linkov
2021-10-12 6:53 ` Juri Linkov
2021-10-12 12:10 ` Lars Ingebrigtsen
2021-10-12 12:34 ` Stefan Monnier
2021-10-12 12:41 ` Lars Ingebrigtsen
2021-10-12 13:18 ` Lars Ingebrigtsen
2021-10-12 13:32 ` Mattias Engdegård
2021-10-12 15:48 ` Stefan Monnier
2021-10-12 13:33 ` Thierry Volpiatto
2021-10-12 19:16 ` Juri Linkov
2021-10-12 20:44 ` Thierry Volpiatto
2021-10-13 7:57 ` Juri Linkov
2021-10-13 8:41 ` Thierry Volpiatto
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=SJ0PR10MB548864DD9DF93CDDBB7A48B7F3A29@SJ0PR10MB5488.namprd10.prod.outlook.com \
--to=drew.adams@oracle.com \
--cc=dgutov@yandex.ru \
--cc=emacs-devel@gnu.org \
--cc=larsi@gnus.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).