all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Nicolas Petton <nicolas@petton.fr>
To: Michael Heerdegen <michael_heerdegen@web.de>,
	Drew Adams <drew.adams@oracle.com>
Cc: 24014@debbugs.gnu.org
Subject: bug#24014: 24.5; doc string of `cl-reduce'
Date: Sun, 17 Jul 2016 23:18:12 +0200	[thread overview]
Message-ID: <878tx0hskr.fsf@petton.fr> (raw)
In-Reply-To: <87zipgmf51.fsf@web.de>

[-- Attachment #1: Type: text/plain, Size: 747 bytes --]

Michael Heerdegen <michael_heerdegen@web.de> writes:

> Drew Adams <drew.adams@oracle.com> writes:
>
>> Please state in the doc string what the function does.  IOW,
>> explain/describe/specify what "reduce" means.  Do not suppose that Emacs
>> Lisp users are all familiar with functional programming etc.

The documentation of `seq-reduce' is probably not perfect, but at least
it tries to explain what reducing means:

    Return the result of calling FUNCTION with INITIAL-VALUE and the
    first element of SEQUENCE, then calling FUNCTION with that result and
    the second element of SEQUENCE, then with that result and the third
    element of SEQUENCE, etc.

    If SEQUENCE is empty, return INITIAL-VALUE and FUNCTION is not called.

Nico

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 512 bytes --]

  reply	other threads:[~2016-07-17 21:18 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-07-17 14:55 bug#24014: 24.5; doc string of `cl-reduce' Drew Adams
2016-07-17 15:57 ` Michael Heerdegen
2016-07-17 21:18   ` Nicolas Petton [this message]
2016-07-18  4:44     ` Drew Adams
2016-07-18 12:19       ` Nicolas Petton
2021-10-23 17:32       ` Stefan Kangas
2016-07-18  4:41   ` Drew Adams
2016-07-18  8:54     ` Clément Pit--Claudel
2016-07-18 14:02       ` Drew Adams
2016-07-18 16:03         ` Clément Pit--Claudel
2016-07-18 17:28           ` Drew Adams

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=878tx0hskr.fsf@petton.fr \
    --to=nicolas@petton.fr \
    --cc=24014@debbugs.gnu.org \
    --cc=drew.adams@oracle.com \
    --cc=michael_heerdegen@web.de \
    /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.