From: Eli Zaretskii <eliz@gnu.org>
To: Michael Heerdegen <michael_heerdegen@web.de>
Cc: larsi@gnus.org, jonas@bernoul.li, 59328@debbugs.gnu.org
Subject: bug#59328: 29.0.50; `seq-keep' implementation only valid for lists
Date: Thu, 24 Nov 2022 16:19:26 +0200 [thread overview]
Message-ID: <83edtswi35.fsf@gnu.org> (raw)
In-Reply-To: <87pmdctsf8.fsf@web.de> (message from Michael Heerdegen on Thu, 24 Nov 2022 14:04:27 +0100)
> From: Michael Heerdegen <michael_heerdegen@web.de>
> Cc: 59328@debbugs.gnu.org, larsi@gnus.org, jonas@bernoul.li
> Date: Thu, 24 Nov 2022 14:04:27 +0100
>
> Eli Zaretskii <eliz@gnu.org> writes:
>
> > > #+begin_src emacs-lisp
> > > (defun seq-keep (function sequence)
> > > (seq-filter #'identity (seq-map function sequence)))
> > > #+end_src
> >
> > This makes sense to me, so please go ahead and install, preferably
> > with a test for non-list cases.
>
> I don't think adding a test case to Emacs is possible - all currently
> existing counterexamples I found (stream.el, myers.el) are in Elpa or
> somewhere else, but not in the Emacs repo.
I don't understand: why cannot we add a test to Emacs, even though other
tests are elsewhere?
> So I guess it's ok to go without a test?
It's okay, but I'd prefer to have a test.
next prev parent reply other threads:[~2022-11-24 14:19 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-17 2:17 bug#59328: 29.0.50; `seq-keep' implementation only valid for lists Michael Heerdegen
2022-11-19 13:12 ` Eli Zaretskii
2022-11-24 13:04 ` Michael Heerdegen
2022-11-24 14:19 ` Eli Zaretskii [this message]
2022-11-24 14:26 ` Michael Heerdegen
2022-11-24 15:00 ` Eli Zaretskii
2022-11-24 15:09 ` Michael Heerdegen
2022-11-24 15:15 ` Eli Zaretskii
2022-11-24 15:25 ` Michael Heerdegen
2022-11-24 17:02 ` Eli Zaretskii
2022-11-25 9:47 ` Michael Heerdegen
2022-11-25 11:34 ` Stefan Kangas
2022-11-25 11:55 ` Eli Zaretskii
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=83edtswi35.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=59328@debbugs.gnu.org \
--cc=jonas@bernoul.li \
--cc=larsi@gnus.org \
--cc=michael_heerdegen@web.de \
/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.