From: "Daniel Martín" <mardani29@yahoo.es>
To: Iwan in 't Groen <iwanintgroen@gmail.com>
Cc: emacs-devel@gnu.org
Subject: Re: Documentation for `seq-contains-p` is outdated
Date: Sat, 29 Aug 2020 20:18:56 +0200 [thread overview]
Message-ID: <m15z91l3hr.fsf@yahoo.es> (raw)
In-Reply-To: <E18CDFB1-55DE-494F-B430-4A2424D88511@gmail.com> (Iwan in t. Groen's message of "Sat, 15 Aug 2020 16:14:19 +0200")
Iwan in 't Groen <iwanintgroen@gmail.com> writes:
> Hi,
>
> When looking up the documentation for `seq-contains-p` it seems
> outdated.
>
> M-x elisp-index-search RET seq-contains-p RET returns:
>
> -- Function: seq-contains-p sequence elt &optional function
> This function returns non-‘nil’ if at least one element in SEQUENCE
> is equal to ELT. If the optional argument FUNCTION is non-‘nil’,
> it is a function of two arguments to use instead of the default
> ‘equal’.
>
> (seq-contains '(symbol1 symbol2) 'symbol1)
> ⇒ symbol1
> (seq-contains '(symbol1 symbol2) 'symbol3)
> ⇒ nil
>
> The title is correct but the information shown is for the obsolete
> `seq-contains` function.
Thank you for your contribution to Emacs. The change looks good to
me. If I'm not mistaken, this new function was introduced in 27.1, so
this might be a safe patch for 27.2. I've only left a comment, but let's
wait for other Emacs developers to do a proper review of this patch
(Nicolas Petton seems like the best person to do so).
>
> diff --git a/doc/lispref/sequences.texi b/doc/lispref/sequences.texi
> index 91c3049f87..bb80307c8c 100644
> --- a/doc/lispref/sequences.texi
> +++ b/doc/lispref/sequences.texi
> @@ -784,18 +784,18 @@ Sequence Functions
>
>
> @defun seq-contains-p sequence elt &optional function
> - This function returns non-@code{nil} if at least one element in
> + This function returns @code{t} if at least one element in
If we change this in the manual, I think we should also change the
documentation string for the function accordingly. I think that the
change makes sense, because seq-contains-p is a yes-or-no predicate and
"Return t if" complies with our tips for documentation strings.
> @var{sequence} is equal to @var{elt}. If the optional argument
> @var{function} is non-@code{nil}, it is a function of two arguments to
> use instead of the default @code{equal}.
>
> @example
> @group
> -(seq-contains '(symbol1 symbol2) 'symbol1)
> -@result{} symbol1
> +(seq-contains-p '(symbol1 symbol2) 'symbol1)
> +@result{} t
> @end group
> @group
> -(seq-contains '(symbol1 symbol2) 'symbol3)
> +(seq-contains-p '(symbol1 symbol2) 'symbol3)
> @result{} nil
> @end group
> @end example
next prev parent reply other threads:[~2020-08-29 18:18 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-15 14:14 Documentation for `seq-contains-p` is outdated Iwan in 't Groen
2020-08-29 18:18 ` Daniel Martín [this message]
2020-08-29 18:40 ` 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=m15z91l3hr.fsf@yahoo.es \
--to=mardani29@yahoo.es \
--cc=emacs-devel@gnu.org \
--cc=iwanintgroen@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 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.