From: Tino Calancha <f92capac@gmail.com>
To: 21782@debbugs.gnu.org
Cc: f92capac@gmail.com
Subject: bug#21782: 25.0.50; New functions nfront/front
Date: Fri, 30 Oct 2015 19:10:00 +0900 (JST) [thread overview]
Message-ID: <alpine.LRH.2.20.1510301858230.12669@calancha-ilc.kek.jp> (raw)
In-Reply-To: <CAAdUY-JTCxOBRjKpfb961metBJVqWdu9bbz87fC1P46jBQ+3wQ@mail.gmail.com>
Thank you.
I agree with your 3 points.
1) Clearly replicate functionality
2) Yes, the prefix prevent to pollute.
3) Agree.
My main concern is why seq-take is not auloaded at the start of the
session. Its natural to have loaded such function always.
Anyway thank you very much.
On Fri, 30 Oct 2015, Artur Malabarba wrote:
>
> On 30 Oct 2015 2:53 am, "Constantino Calancha" <f92capac@gmail.com> wrote:
> > Why i need to pollute my global space with all seq.el just to use this
> > fundamental operation on a list?
>
> I think, overall, sticking to seq-take has a smaller cost/benefit ratio than adding nfront. I state my logic below.
>
> These points are all a little subjective. So if you disagree and think that
the slider falls closer to the other side, we can wait to hear more opinions (though at least Michael seems to
> agree).
>
> 1. While nfront is not identical to seq-take, it's similar enough that this would just be replicating functionality, which is ultimately a maintenance burden.
> 2. Seq is not a huge lib, so you're not polluting that much. Furthermore, all its functions are prefixed by "seq-", so you're polluting even less. Lastly, seq was added to core
> specifically with the purpose of being the goto sequences lib (and it's been doing that fine), so it wouldn't make sense to circumvent it now.
> 3. I'm of the opinion that we should be adding namespace prefixes as much as possible. Unprefixed names pollute much more and are harder to find.
>
> In any case, thanks for the suggestion.
>
>
>
next prev parent reply other threads:[~2015-10-30 10:10 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 [this message]
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=alpine.LRH.2.20.1510301858230.12669@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.