From: "Constantino Calancha" <f92capac@gmail.com>
To: "21782@debbugs.gnu.org" <21782@debbugs.gnu.org>
Cc: f92capac@gmail.com
Subject: bug#21782: 25.0.50; New functions nfront/front
Date: Fri, 30 Oct 2015 11:53:30 +0900 [thread overview]
Message-ID: <op.x7aszghd32915k@calancha-ilc.kek.jp> (raw)
In-Reply-To: <87wpu5jd1y.fsf@web.de>
Im sorry Michael, but i dont see your point: do you mean the fact to call
nreverse twice?
nreverse is in fact very efficient;
and last already use nthcdr in its implementation.
Please elaborate more.
As i mentioned, they are not exactly the same function as seq-take.
Why i need to pollute my global space with all seq.el just to use this
fundamental operation on a list?
I we want this in the core, we may also consider to implement such
functionality in
src/fns.c
Tino
On Fri, 30 Oct 2015 11:38:33 +0900, Michael Heerdegen
<michael_heerdegen@web.de> wrote:
> Tino Calancha <f92capac@gmail.com> writes:
>
>> + (nreverse (last (nreverse list) n))))
>
> Isn't this horribly inefficient? It would be better to use `nthcdr' or
> a simple loop.
>
> Dunno if this should be in the core, I think having this functionality
> in "seq.el" is a good place.
>
>
> Michael.
next prev parent reply other threads:[~2015-10-30 2:53 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-29 9:57 bug#21782: 25.0.50; New functions nfront/front Tino Calancha
2015-10-29 15:25 ` Artur Malabarba
2015-10-30 1:25 ` Tino Calancha
2015-10-30 2:38 ` Michael Heerdegen
2015-10-30 2:53 ` Constantino Calancha [this message]
2015-10-30 9:45 ` Artur Malabarba
2015-10-30 10:10 ` Tino Calancha
2015-10-30 10:03 ` Nicolas Petton
2015-10-30 10:11 ` Tino Calancha
2015-10-30 14:09 ` Michael Heerdegen
2015-10-30 18:06 ` Tino Calancha
2015-10-30 2:10 ` Tino Calancha
2015-10-30 1:33 ` Richard Stallman
2015-10-30 1:41 ` Constantino Calancha
[not found] ` <mailman.1293.1446168906.7904.bug-gnu-emacs@gnu.org>
2015-10-31 22:44 ` Alan Mackenzie
2017-05-18 4:08 ` Tino Calancha
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=op.x7aszghd32915k@calancha-ilc.kek.jp \
--to=f92capac@gmail.com \
--cc=21782@debbugs.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.