From: Bozhidar Batsov <bozhidar@batsov.com>
To: Michael Heerdegen <michael_heerdegen@web.de>
Cc: Nicolas Petton <nicolas@petton.fr>, David Kastrup <dak@gnu.org>,
emacs-devel <emacs-devel@gnu.org>
Subject: Re: seq-thread-first/last
Date: Fri, 30 Jan 2015 14:58:18 +0200 [thread overview]
Message-ID: <CAM9Zgm2gHZHFcQJ706TPce0wyjDbg__z+JfnE30QBaELJM409g@mail.gmail.com> (raw)
In-Reply-To: <87pp9wwiqh.fsf@web.de>
[-- Attachment #1: Type: text/plain, Size: 1063 bytes --]
thread-first and thread-last have nothing to do with sequences, so I think
there's nothing to do about them in regards to seq.el.
On 30 January 2015 at 14:33, Michael Heerdegen <michael_heerdegen@web.de>
wrote:
> David Kastrup <dak@gnu.org> writes:
>
> > Hard to corroborate if the people mentioning their wishes don't bother
> > mentioning what their desired functions are supposed to do.
>
> Do you mean me? I thought my explanation was clear. Anyway, the
> semantic would be like this:
>
> --8<---------------cut here---------------start------------->8---
>
> (defmacro seq-thread-first (seq &rest forms)
> (declare (indent 1))
> (let ((x (make-symbol "x")))
> `(seq-map (lambda (,x) (thread-first ,x ,@forms)) ,seq)))
> --8<---------------cut here---------------end--------------->8---
>
> though that's probably not the most efficient implementation.
> seq-thread-last analog.
>
> Example:
>
> (seq-thread-first (number-sequence 1 3)
> (* 10) (+ 1))
>
> ==> (11 21 31)
>
>
> Or was your critique about use cases?
>
>
> Thanks,
>
> Michael.
>
>
[-- Attachment #2: Type: text/html, Size: 1591 bytes --]
next prev parent reply other threads:[~2015-01-30 12:58 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 ` seq-thread-first/last Nicolas Petton
2015-01-30 12:33 ` seq-thread-first/last Michael Heerdegen
2015-01-30 12:58 ` Bozhidar Batsov [this message]
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CAM9Zgm2gHZHFcQJ706TPce0wyjDbg__z+JfnE30QBaELJM409g@mail.gmail.com \
--to=bozhidar@batsov.com \
--cc=dak@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=michael_heerdegen@web.de \
--cc=nicolas@petton.fr \
/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.