unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Drew Adams <drew.adams@oracle.com>
To: 42324@debbugs.gnu.org
Subject: bug#42324: 26.3; Doc string of `seq-concatenate'
Date: Sat, 11 Jul 2020 09:10:36 -0700 (PDT)	[thread overview]
Message-ID: <efa23108-da23-4a5b-8bd7-23f25007bed0@default> (raw)

C-h f seq-concatenate
___

 seq-concatenate is a compiled Lisp function in 'seq.el'.

 (seq-concatenate TYPE SEQUENCE...)

 Concatenate SEQUENCES into a single sequence of type TYPE.
 TYPE must be one of following symbols: vector, string or list.


 This is a generic function.

 Implementations:

 (type &rest sequences) in 'seq.el'.

 Undocumented
___

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?


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''





             reply	other threads:[~2020-07-11 16:10 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-07-11 16:10 Drew Adams [this message]
2020-08-25 22:24 ` bug#42324: 26.3; Doc string of `seq-concatenate' Stefan Kangas
2020-08-25 22:46   ` Drew Adams
2020-08-26  6:00     ` Eli Zaretskii
     [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
     [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
2020-08-26 18:57             ` Eli Zaretskii
2020-08-27 14:27               ` Lars Ingebrigtsen

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=efa23108-da23-4a5b-8bd7-23f25007bed0@default \
    --to=drew.adams@oracle.com \
    --cc=42324@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).