From: Tino Calancha <f92capac@gmail.com>
To: Michael Heerdegen <michael_heerdegen@web.de>
Cc: Constantino Calancha <f92capac@gmail.com>,
"21782@debbugs.gnu.org" <21782@debbugs.gnu.org>
Subject: bug#21782: 25.0.50; New functions nfront/front
Date: Sat, 31 Oct 2015 03:06:40 +0900 (JST) [thread overview]
Message-ID: <alpine.LRH.2.20.1510310251500.15175@calancha-ilc.kek.jp> (raw)
In-Reply-To: <87a8r0sb21.fsf@web.de>
>
> `nreverse` efficiently does what is supposed to do, yes. But it is
> O(l), where l is the length of the list arg.
>
> In addition, the newly created `nreverse'd list must be garbage
> collected.
>
> The `copy-sequence' call in `front' is bad for the same reason.
>
> OTOH nfront can be implemented in O(n), where n is the number argument
> to nfront.
Thank you Michael for the detail answer. I appreciate it a lot.
Now i see clearly what you mean.
For all the people:
Efficiency implementations are very important, almost as important as
have things available.
One emacs user starting one session has no available seq-take. That is
the first thing to care, efficiency comes later.
Many users learn the lenguage autocompleting in the minibuffer. If it is
not loaded the least people will realize such functions you are
developping do exists. We develop tools to be used, not ust to be nice.
IMOP, fundamental operations should be loaded by default. If this is not
the case, that means the function should not be located in its corrent
location: fair and simple.
Please, consider make this fundamental operation being loaded at the
beginning. Thanks.
I finish here because i start to repeat myself. Thank you for the very
nice chat; it has being very instructive for me and i enjoied very much.
next prev parent reply other threads:[~2015-10-30 18:06 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
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 [this message]
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
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=alpine.LRH.2.20.1510310251500.15175@calancha-ilc.kek.jp \
--to=f92capac@gmail.com \
--cc=21782@debbugs.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).