unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Stefan Monnier <monnier@iro.umontreal.ca>
To: emacs-devel@gnu.org
Subject: Re: Should `position' be implemented in Emacs core and preloaded?
Date: Wed, 05 Oct 2016 11:50:55 -0400	[thread overview]
Message-ID: <jwv60p64xbh.fsf-monnier+gmane.emacs.devel@gnu.org> (raw)
In-Reply-To: alpine.DEB.2.20.1610060023400.6795@calancha-pc

> What i meant is that it would be nice if people could use that kind of
> useful functions without face resistances.  I saw before
> in this list people who wanted to use a function from cl-lib or seq.el,
> and they received objections because that would force that file to
> require such lib.

Normally such resistance only appears when it would require preloading
seq or cl-lib (i.e. when it's used by a file which is itself preloaded).

I think preloading seq.el would be OK under the following conditions:
- seq.el is changed so as not to require cl-lib (that's mostly
  a question of moving shared code between the two libs so that it's in
  seq.el instead of in cl-lib, so it shouldn't be too difficult).
- one of the preloaded files really benefits from seq.el.

>> Also, FWIW, I don't see many uses of these cl/seq-position functions
>> in Emacs, so I'm not sure how important they are, really.
> I suspect that one important reason to not appear widely is exactly
> that in order to use them we need to require the lib to use it.

You might be right.  I guess there's also the fact that on singly-linked
lists, using seq-position is rarely the best way (in terms of
efficiency) to get the job done.


        Stefan




  reply	other threads:[~2016-10-05 15:50 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-10-05 14:46 Should `position' be implemented in Emacs core and preloaded? Tino Calancha
2016-10-05 15:13 ` Stefan Monnier
2016-10-05 15:37   ` Tino Calancha
2016-10-05 15:50     ` Stefan Monnier [this message]
2016-10-05 16:14       ` 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=jwv60p64xbh.fsf-monnier+gmane.emacs.devel@gnu.org \
    --to=monnier@iro.umontreal.ca \
    --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 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).