From: Stefan Monnier <monnier@iro.umontreal.ca>
To: Nicolas Petton <nicolas@petton.fr>
Cc: emacs-devel@gnu.org
Subject: Re: [Emacs-diffs] master 387e1e1: New version of `seq-let' based on a pcase pattern
Date: Mon, 11 May 2015 11:06:31 -0400 [thread overview]
Message-ID: <jwvfv7317sr.fsf-monnier+emacsdiffs@gnu.org> (raw)
In-Reply-To: <874mnjdycw.fsf@petton.fr> (Nicolas Petton's message of "Mon, 11 May 2015 15:42:39 +0200")
> Yes. My idea of it was that you bind a sequence like the following:
> (seq [a b [c d]])
I was thinking of (seq a b (seq c d)).
You could add support for (seq a b [c d]), if you want since that
currently wouldn't collide with any pcase pattern, tho I'm not sure it's
worth the added complexity for the user.
> But then how can I have `seq-let' work the way it did until now? For
> instance:
> (seq-let [a [b [c]]] my-vector
> ...)
You expand [a [b [c]]] to (seq a (seq b (seq c))) before passing it to
pcase-let.
>>> + (push `(app (seq--reverse-args #'seq--nested-elt
>>> + (reverse (cons ,index ',nested-indexes)))
>>> + ,name)
>> This reverse plus seq--reverse-args business seems
>> hideously inefficient. Why do you need that?
> because of the way the `app' pattern works. Or maybe I'm missing
> something?
Why wouldn't
`(app (seq--nested-elt ',(reverse (cons index nested-indexes))) ,name)
work as well? Or, once you get rid of the nested case,
`(app (seq-elt ,index) ,name)
-- Stefan
next prev parent reply other threads:[~2015-05-11 15:06 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20150510182502.23307.63648@vcs.savannah.gnu.org>
[not found] ` <E1YrVuR-00064X-CK@vcs.savannah.gnu.org>
2015-05-11 4:15 ` [Emacs-diffs] master 387e1e1: New version of `seq-let' based on a pcase pattern Stefan Monnier
2015-05-11 13:42 ` Nicolas Petton
2015-05-11 15:06 ` Stefan Monnier [this message]
2015-05-11 21:13 ` Nicolas Petton
2015-05-11 21:35 ` Nicolas Petton
2015-05-12 1:03 ` Stefan Monnier
2015-05-12 6:51 ` Nicolas Petton
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=jwvfv7317sr.fsf-monnier+emacsdiffs@gnu.org \
--to=monnier@iro.umontreal.ca \
--cc=emacs-devel@gnu.org \
--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.