From: Ihor Radchenko <yantar92@posteo.net>
To: Stefan Monnier <monnier@iro.umontreal.ca>
Cc: Stefan Kangas <stefankangas@gmail.com>, 68370@debbugs.gnu.org
Subject: bug#68370: 30.0.50; pcase eieio, map, seq, and cl-struct constructs are not described in the manual
Date: Fri, 12 Jan 2024 12:47:42 +0000 [thread overview]
Message-ID: <87sf32pvkh.fsf@localhost> (raw)
In-Reply-To: <jwvr0innte6.fsf-monnier+emacs@gnu.org>
Stefan Monnier <monnier@iro.umontreal.ca> writes:
>>> AFAIK these "belong" to `map.el`, `seq.el`, etc... so that's where they
>>> should be documented. The documentation for `pcase` could of course
>>> include corresponding cross-references.
>> Do you mean "6.1 Sequences" section of the manual?
>
> I meant "where ever it's documented", so yes that sounds about right :-)
This might be tricky in practice:
1. eieio is more or less clear - it is a separate manual
2. seq.el is documented in 6.1 section, which may be a problem - the
very concept of pattern matching is only introduced in 11.4.1 (pcase)
section. So, it might be confusing for the readers to see information
about pattern matching so early in the manual.
3. map.el does not have any documentation in manual. It may mean that
(map ..) pattern should not be documented. Or it may mean that we
need to add a map.el section to the manual.
4. 11.4.1 The ‘pcase’ macro section already documents ‘(cl-type TYPE)’,
but not (cl-struct TYPE &rest FIELDS). It will be awkward to document
cl-struct pattern in CL manual, while leaving cl-type in the 11.4.1
section of the Elisp manual.
--
Ihor Radchenko // yantar92,
Org mode contributor,
Learn more about Org mode at <https://orgmode.org/>.
Support Org development at <https://liberapay.com/org-mode>,
or support my work at <https://liberapay.com/yantar92>
next prev parent reply other threads:[~2024-01-12 12:47 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-10 12:46 bug#68370: 30.0.50; pcase eieio, map, seq, and cl-struct constructs are not described in the manual Ihor Radchenko
2024-01-10 14:56 ` Stefan Kangas
2024-01-10 16:19 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-01-11 12:44 ` Ihor Radchenko
2024-01-12 3:06 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-01-12 12:47 ` Ihor Radchenko [this message]
2024-01-13 3:54 ` Richard Stallman
2024-01-12 4:00 ` Richard Stallman
2024-01-13 3:50 ` Richard Stallman
2024-01-13 13:31 ` Ihor Radchenko
2024-01-11 19:09 ` Jim Porter
2024-01-12 23:07 ` Ihor Radchenko
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=87sf32pvkh.fsf@localhost \
--to=yantar92@posteo.net \
--cc=68370@debbugs.gnu.org \
--cc=monnier@iro.umontreal.ca \
--cc=stefankangas@gmail.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).