From: Nicolas Petton <nicolas@petton.fr>
To: Constantino Calancha <f92capac@gmail.com>,
"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:03:50 +0100 [thread overview]
Message-ID: <877fm4zn95.fsf@petton.fr> (raw)
In-Reply-To: <op.x7aszghd32915k@calancha-ilc.kek.jp>
[-- Attachment #1: Type: text/plain, Size: 822 bytes --]
Constantino Calancha <f92capac@gmail.com> writes:
Hi,
> As i mentioned, they are not exactly the same function as seq-take.
I think adding these functions would mostly be code duplication. Please
bear in mind that seq.el was written to provide a good built-in sequence
library in Emacs. If seq-take doesn't provide exactly what you need,
you could propose a patch to improve it instead.
> Why i need to pollute my global space with all seq.el just to use this
> fundamental operation on a list?
All functions in seq.el are prefixed, so there's no global namespace
polluting, and I consider many functions provided by seq.el to be
fundamental operations on sequences.
Also, seq.el is not pre-loaded today because it's a new library, so it
is not widely used in Emacs yet, but that could change in the future.
Nico
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 512 bytes --]
next prev parent reply other threads:[~2015-10-30 10:03 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 [this message]
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
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=877fm4zn95.fsf@petton.fr \
--to=nicolas@petton.fr \
--cc=21782@debbugs.gnu.org \
--cc=f92capac@gmail.com \
/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).