From: Nicolas Petton <nicolas@petton.fr>
To: David Kastrup <dak@gnu.org>
Cc: Michael Heerdegen <michael_heerdegen@web.de>,
Nicolas Petton <nicolas@petton.fr>,
emacs-devel@gnu.org
Subject: Re: seq-thread-first/last
Date: Fri, 30 Jan 2015 13:25:05 +0100 [thread overview]
Message-ID: <87d25we9r2.fsf@petton.fr> (raw)
In-Reply-To: <87wq44a2f3.fsf@fencepost.gnu.org>
David Kastrup <dak@gnu.org> writes:
>> thread-first/last are not in elisp though, are they?
>
> Hard to corroborate if the people mentioning their wishes don't bother
> mentioning what their desired functions are supposed to do.
Sorry about that. Here's the docstring of `thread-first' from subr-x.el:
Thread FORMS elements as the first argument of their successor.
Example:
(thread-first
5
(+ 20)
(/ 25)
-
(+ 40))
Is equivalent to:
(+ (- (/ (+ 5 20) 25)) 40)
Note how the single `-' got converted into a list before
threading.
Cheers,
Nico
--
Nicolas Petton
http://nicolas-petton.fr
next prev parent reply other threads:[~2015-01-30 12:25 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-29 16:54 Would seq-range and seq-mapcat be useful? Nicolas Petton
2015-01-29 18:02 ` Artur Malabarba
2015-01-29 22:03 ` Nicolas Petton
2015-01-29 21:40 ` Stefan Monnier
2015-01-29 22:06 ` Nicolas Petton
2015-01-30 6:09 ` Stefan Monnier
2015-01-30 8:00 ` Oleh Krehel
2015-01-30 10:21 ` Nicolas Petton
2015-01-30 15:38 ` Oleh Krehel
2015-01-30 15:59 ` Nicolas Richard
2015-01-30 16:04 ` Oleh Krehel
2015-01-30 16:05 ` Oleh Krehel
2015-01-30 16:36 ` Nicolas Richard
2015-01-30 16:51 ` Oleh Krehel
2015-01-30 16:23 ` Nicolas Petton
2015-02-02 0:11 ` Nicolas Petton
2015-02-02 7:49 ` Oleh Krehel
2015-02-02 9:28 ` Nicolas Petton
2015-02-02 18:34 ` Mark Oteiza
2015-02-02 18:39 ` Oleh Krehel
2015-02-04 12:02 ` Ted Zlatanov
2015-01-30 8:20 ` What about seq-slice? (Was: Would seq-range and seq-mapcat be useful?) Mark Oteiza
2015-01-30 10:25 ` Nicolas Petton
2015-01-30 11:09 ` seq-thread-first/last (was: What about seq-slice?) Michael Heerdegen
2015-01-30 11:59 ` Nicolas Petton
2015-01-30 12:08 ` seq-thread-first/last Michael Heerdegen
2015-01-30 12:21 ` seq-thread-first/last Nicolas Petton
2015-01-30 12:17 ` seq-thread-first/last David Kastrup
2015-01-30 12:25 ` Nicolas Petton [this message]
2015-01-30 12:33 ` seq-thread-first/last Michael Heerdegen
2015-01-30 12:58 ` seq-thread-first/last Bozhidar Batsov
2015-01-30 14:02 ` seq-thread-first/last Artur Malabarba
2015-01-30 14:15 ` seq-thread-first/last Michael Heerdegen
2015-01-30 17:17 ` What about seq-slice? Mark Oteiza
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=87d25we9r2.fsf@petton.fr \
--to=nicolas@petton.fr \
--cc=dak@gnu.org \
--cc=emacs-devel@gnu.org \
--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 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).