From: Lars Ingebrigtsen <larsi@gnus.org>
To: Drew Adams <drew.adams@oracle.com>
Cc: 42323@debbugs.gnu.org
Subject: bug#42323: 26.3; Doc string of `seq-map'
Date: Wed, 09 Dec 2020 14:41:58 +0100 [thread overview]
Message-ID: <87ft4f3xll.fsf@gnus.org> (raw)
In-Reply-To: <c1fc9e80-6604-4ee7-a1d8-3f7851f2e627@default> (Drew Adams's message of "Sat, 11 Jul 2020 09:01:25 -0700 (PDT)")
Drew Adams <drew.adams@oracle.com> writes:
> Or IF understanding the implementation is really necessary, then the
> fact that seq.el is implemented using cl constructs can't be elided.
This is the current doc string:
---
seq-map is a compiled Lisp function in ‘seq.el’.
(seq-map FUNCTION SEQUENCE)
Other relevant functions are documented in the sequence group.
Return the result of applying FUNCTION to each element of SEQUENCE.
This is a generic function.
Implementations:
#'(sequence sequence) in ‘seq.el’.
Undocumented
#'sequence in ‘seq.el’.
Undocumented
---
It is, indeed, pretty obscure. Like Drew, I wonder -- do we really have
to put these implementation details in the doc string at all? Opinions?
--
(domestic pets only, the antidote for overdose, milk.)
bloggy blog: http://lars.ingebrigtsen.no
next prev parent reply other threads:[~2020-12-09 13:41 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-11 16:01 bug#42323: 26.3; Doc string of `seq-map' Drew Adams
2020-12-09 13:41 ` Lars Ingebrigtsen [this message]
2020-12-09 16:11 ` Michael Heerdegen
2020-12-09 16:44 ` Lars Ingebrigtsen
2020-12-09 19:24 ` Michael Heerdegen
2020-12-09 20:00 ` Drew Adams
2020-12-09 20:19 ` Lars Ingebrigtsen
2021-09-25 15:25 ` Stefan Kangas
2021-09-25 16:10 ` bug#42323: [External] : " Drew Adams
2021-09-25 16:21 ` Eli Zaretskii
2021-09-25 16:43 ` Stefan Kangas
2021-09-25 16:28 ` Stefan Kangas
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=87ft4f3xll.fsf@gnus.org \
--to=larsi@gnus.org \
--cc=42323@debbugs.gnu.org \
--cc=drew.adams@oracle.com \
/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).