From: Pip Cet via "Emacs development discussions." <emacs-devel@gnu.org>
To: "Mattias Engdegård" <mattias.engdegard@gmail.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 10:56:26 +0000 [thread overview]
Message-ID: <87ed1w9glz.fsf@protonmail.com> (raw)
In-Reply-To: <350E9109-04F6-4C20-B0F6-37C0A482DAD3@gmail.com>
Mattias Engdegård <mattias.engdegard@gmail.com> writes:
> 24 dec. 2024 kl. 22.33 skrev Pip Cet via Emacs development discussions. <emacs-devel@gnu.org>:
>
>> I think the OP meant that (nth -1 '(1 2)) is 1 on current Emacs, which
>> is definitely unexpected.
>
> It's a straight consequence of (nth N L) = (car (nthcdr N L)).
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.
(My apologies for actually writing about nthcdr but calling it nth in
the last mail).
>>> I don't see a strong argument in favor of making it index from the end
>>> rather than signal an error. What would the implementation look like?
>>
>> I agree, but the current implementation does not signal an error. It
>> should, and I think that's what the suggestion was.
>
> It is true that signalling an error for negative arguments might catch
> some bugs but doing so would also risk breaking working code that
> relies on the current (well-defined) behaviour.
If it were merely undocumented, I might agree, but the current behavior
doesn't match the documentation, because taking cdr -1 times is
obviously an impossible thing to do.
> And there's not much performance to gain from it
This isn't about performance.
Pip
next prev parent reply other threads:[~2024-12-25 10:56 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. [this message]
2024-12-25 12:14 ` Mattias Engdegård
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87ed1w9glz.fsf@protonmail.com \
--to=emacs-devel@gnu.org \
--cc=atamariya@gmail.com \
--cc=eliz@gnu.org \
--cc=mattias.engdegard@gmail.com \
--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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.