all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Artur Malabarba <bruce.connor.am@gmail.com>
To: emacs-devel <emacs-devel@gnu.org>
Subject: Re: [Request] seq-map and mapcar with arbitrary number of sequences
Date: Sat, 10 Oct 2015 22:53:20 +0100	[thread overview]
Message-ID: <CAAdUY-+B8XutSH-rOn9o-C+uvrnbt0o-oraBBGRENn3heyNjgA@mail.gmail.com> (raw)
In-Reply-To: <m2bnc6iiwp.fsf@newartisans.com>

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

Yes. Supporting this on mapc and mapcar should not incur a performance cost
on the single seq version. I figured the c code for these functions could
just check if the &rest argument is nil, and then use the current (single
seq) implementation.

If this single conditional imposes a noticeable overhead we can optimise it
out with a compiler macro too (I think).
On 10 Oct 2015 9:10 pm, "John Wiegley" <johnw@newartisans.com> wrote:

> >>>>> David Kastrup <dak@gnu.org> writes:
>
> > The byte compiler should be able to squash the difference, right?
>
> If you can demonstrate that to me, I'm sold. As long as the C code doesn't
> change, and the increase in complexity vanishes at byte-compilation time, I
> have no argument.
>
> John
>
>

[-- Attachment #2: Type: text/html, Size: 1106 bytes --]

  reply	other threads:[~2015-10-10 21:53 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-10-10  7:24 [Request] seq-map and mapcar with arbitrary number of sequences bruce.connor.am
2015-10-10 17:47 ` John Wiegley
2015-10-10 17:58   ` David Kastrup
2015-10-10 20:10     ` John Wiegley
2015-10-10 21:53       ` Artur Malabarba [this message]
2015-10-10 23:24         ` John Wiegley
2015-10-11 20:36           ` Nicolas Petton
2015-10-11 20:48             ` John Wiegley
2015-10-11 20:51   ` Richard Stallman
2015-10-11 21:10     ` Nicolas Petton
2015-10-12  9:27       ` Michael Heerdegen
2015-10-13 12:42   ` David Kastrup

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=CAAdUY-+B8XutSH-rOn9o-C+uvrnbt0o-oraBBGRENn3heyNjgA@mail.gmail.com \
    --to=bruce.connor.am@gmail.com \
    --cc=emacs-devel@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 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.