From: "Mattias Engdegård" <mattias.engdegard@gmail.com>
To: Pip Cet <pipcet@protonmail.com>
Cc: Stefan Monnier <monnier@iro.umontreal.ca>,
Stefan Kangas <stefankangas@gmail.com>,
Tassilo Horn <tsdh@gnu.org>, Eli Zaretskii <eliz@gnu.org>,
Anand Tamariya <atamariya@gmail.com>,
emacs-devel@gnu.org
Subject: Re: Negative nth index
Date: Wed, 25 Dec 2024 13:14:05 +0100 [thread overview]
Message-ID: <5D930F52-CD28-4E5E-89B2-1E9DC3945011@gmail.com> (raw)
In-Reply-To: <87ed1w9glz.fsf@protonmail.com>
25 dec. 2024 kl. 11.56 skrev Pip Cet <pipcet@protonmail.com>:
> s/nth/nthcdr/g in my email, then. Of course the two should behave
> analogously, the question is whether they should both throw an error (my
> opinion) or shouldn't.
The behaviour of nthcdr for negative N is well-established and turns out to be somewhat useful in practice.
If compatibility with existing code were completely unimportant, I'd recommend that negative arguments cause nth to signal but not nthcdr. But it isn't, so I don't.
> If it were merely undocumented, I might agree, but the current behavior
> doesn't match the documentation,
Yes, the manual and doc strings could certainly be improved.
> because taking cdr -1 times is
> obviously an impossible thing to do.
Well now, we could define
(nthcdr N L) = (cons nil (nthcdr (1+ N) L)
for N<0. (No, we shouldn't.)
> This isn't about performance.
Of course it's about performance. In some respect it always is!
next prev parent reply other threads:[~2024-12-25 12:14 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-22 5:43 Negative nth index Anand Tamariya
2024-12-22 7:39 ` Eli Zaretskii
2024-12-22 9:01 ` Tassilo Horn
2024-12-23 5:40 ` Stefan Kangas
2024-12-24 5:11 ` Stefan Monnier
2024-12-24 6:42 ` Teemu Likonen
2024-12-24 6:48 ` Thierry Volpiatto
2024-12-24 13:09 ` Philip Kaludercic
2024-12-24 15:18 ` Stefan Monnier
2024-12-24 15:24 ` Sebastián Monía
2024-12-24 21:33 ` Pip Cet via Emacs development discussions.
2024-12-25 10:30 ` Mattias Engdegård
2024-12-25 10:56 ` Pip Cet via Emacs development discussions.
2024-12-25 12:14 ` Mattias Engdegård [this message]
2024-12-25 13:04 ` Pip Cet via Emacs development discussions.
2024-12-25 14:23 ` Stefan Kangas
2024-12-25 17:22 ` Stefan Monnier
2024-12-25 14:18 ` Stefan Kangas
2024-12-22 10:16 ` Andreas Schwab
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=5D930F52-CD28-4E5E-89B2-1E9DC3945011@gmail.com \
--to=mattias.engdegard@gmail.com \
--cc=atamariya@gmail.com \
--cc=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=monnier@iro.umontreal.ca \
--cc=pipcet@protonmail.com \
--cc=stefankangas@gmail.com \
--cc=tsdh@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).