From: Drew Adams <drew.adams@oracle.com>
To: 42323@debbugs.gnu.org
Subject: bug#42323: 26.3; Doc string of `seq-map'
Date: Sat, 11 Jul 2020 09:01:25 -0700 (PDT) [thread overview]
Message-ID: <c1fc9e80-6604-4ee7-a1d8-3f7851f2e627@default> (raw)
C-h f seq-map
___
seq-map is a compiled Lisp function in 'seq.el'.
(seq-map FUNCTION SEQUENCE)
Return the result of applying FUNCTION to each element of SEQUENCE.
This is a generic function.
Implementations:
(function (sequence sequence)) in 'seq.el'.
Undocumented
(function sequence) in 'seq.el'.
Undocumented
___
This doc doesn't stand on its own at all, beyond the first line. It
doesn't look other Emacs doc strings. It reads like some text generated
primitively by computer, with no real care about readers/users.
You can't have a clue about what "Implementations:" means, or the
individual implementation descriptions mean, unless you know about
`cl-defgeneric' and `cl-defmethod'.
At the very least there should be some link to the doc of those, or
(preferably) a description of what's involved by saying "This is a
generic function" - IF that's really necessary to understanding
`seq-map'.
Elisp users shouldn't be expected to be proficient in Common Lisp. They
should be able to use and understand a function such as `seq-map'
without caring about its implementation. seq.el constructs should be
describable and described on their own, ideally without requiring users
to dig into Common Lisp constructs.
Or IF understanding the implementation is really necessary, then the
fact that seq.el is implemented using cl constructs can't be elided. Is
that really the case? What we have now is a pretty useless, and quite
confusing, indirect/implicit reference to a cl implementation. Why?
How is that helpful?
In GNU Emacs 26.3 (build 1, x86_64-w64-mingw32)
of 2019-08-29
Repository revision: 96dd0196c28bc36779584e47fffcca433c9309cd
Windowing system distributor `Microsoft Corp.', version 10.0.18362
Configured using:
`configure --without-dbus --host=x86_64-w64-mingw32
--without-compress-install 'CFLAGS=-O2 -static -g3''
next reply other threads:[~2020-07-11 16:01 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-11 16:01 Drew Adams [this message]
2020-12-09 13:41 ` bug#42323: 26.3; Doc string of `seq-map' Lars Ingebrigtsen
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=c1fc9e80-6604-4ee7-a1d8-3f7851f2e627@default \
--to=drew.adams@oracle.com \
--cc=42323@debbugs.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).