From: Drew Adams <drew.adams@oracle.com>
To: Eli Zaretskii <eliz@gnu.org>, Drew Adams <drew.adams@oracle.com>
Cc: 42324@debbugs.gnu.org, stefan@marxist.se
Subject: bug#42324: 26.3; Doc string of `seq-concatenate'
Date: Wed, 26 Aug 2020 11:37:39 -0700 (PDT) [thread overview]
Message-ID: <e769db1c-c177-430e-87b5-77b2013e7983@default> (raw)
In-Reply-To: <<83mu2h2rah.fsf@gnu.org>>
> > The bug report is not about the implementation at
> > all. It's about the doc specifying the behavior.
>
> The doc string seems clear to me. And since I don't understand what
> are #1, #2, and #3 in your notation, I cannot continue this discussion
> in any useful way, sorry.
From the bug report (and elsewhere in the thread I
also made clear what #1, #2, and #3 referred to):
1. See bug #42323 for the problem of the unhelpful,
implicit reference to CL implementations and
"generic function".
2. The doc of `seq-concatenate' _really_ needs a
description of how it differs from `cl-concatenate'.
That's completely unclear.
3. The doc says nothing about each SEQUENCE actually
being automatically converted (by copying, presumably)
into a real sequence: `seq-into-sequence'. It's
not clear what's allowed as SEQUENCE.
#2 is the main reason I filed this bug report. What's the difference?
Why/when would you use one rather than the other?
next parent reply other threads:[~2020-08-26 18:37 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <<<efa23108-da23-4a5b-8bd7-23f25007bed0@default>
[not found] ` <<<CADwFkmma0jyd8P0CNqXp80KghqSqkdFS_fHsMm3v2cXMKmEEqw@mail.gmail.com>
[not found] ` <<<f5df3cc5-3fad-4295-9f67-e2359317832a@default>
[not found] ` <<<83a6yi3q0p.fsf@gnu.org>
[not found] ` <<a12959b1-2625-49b8-82df-004a3f6afaa4@default>
[not found] ` <<83mu2h2rah.fsf@gnu.org>
2020-08-26 18:37 ` Drew Adams [this message]
2020-08-26 18:57 ` bug#42324: 26.3; Doc string of `seq-concatenate' Eli Zaretskii
2020-08-27 14:27 ` Lars Ingebrigtsen
[not found] <<efa23108-da23-4a5b-8bd7-23f25007bed0@default>
[not found] ` <<CADwFkmma0jyd8P0CNqXp80KghqSqkdFS_fHsMm3v2cXMKmEEqw@mail.gmail.com>
[not found] ` <<f5df3cc5-3fad-4295-9f67-e2359317832a@default>
[not found] ` <<83a6yi3q0p.fsf@gnu.org>
2020-08-26 18:14 ` Drew Adams
2020-08-26 18:30 ` Eli Zaretskii
2020-07-11 16:10 Drew Adams
2020-08-25 22:24 ` Stefan Kangas
2020-08-25 22:46 ` Drew Adams
2020-08-26 6:00 ` 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=e769db1c-c177-430e-87b5-77b2013e7983@default \
--to=drew.adams@oracle.com \
--cc=42324@debbugs.gnu.org \
--cc=eliz@gnu.org \
--cc=stefan@marxist.se \
/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.