[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Making seq.el an Elpa core package?

From: Phillip Lord
Subject: Re: Making seq.el an Elpa core package?
Date: Sun, 10 Mar 2019 11:48:50 +0000
User-agent: Gnus/5.13 (Gnus v5.13) Emacs/26.1.90 (gnu/linux)

Nicolas Petton <address@hidden> writes:

> Juri Linkov <address@hidden> writes:
>> This package is so useful that it should be preloaded in loadup.el.
> As of today seq.el requires cl-lib, but I think I could easily get rid
> of the dependency.  Anyway IIRC this was discussed some years ago when I
> started working on seq.el, and at the time I also thought such a library
> should come preloaded, but the opinion on this list was quite divided.

I think that there is a lot to be said for explicit dependencies between
packages and minimizing the number of things that are pre-loaded. Most
packages load so quickly these days that the user rarely notices; or
wouldn't if we removed the "loading" messages.

>> It introduces to Elisp programming many necessary idioms that are
>> expected from any modern programming language to help writing more
>> clear and readable code.
> Thanks, I'm glad you like it :-)
>> Recently I implemented a new feature for isearch using seq.el.
>> The resulting code is much shorter with seq than it would be
>> when using ugly old style like `(delq nil (mapcar ...))'.
>> But I can't submit a patch for isearch.el because currently
>> seq.el is not loaded by default.
> Oh right, because isearch.el is itself preloaded.

What would happen is isearch.el were not pre-loaded?


reply via email to

[Prev in Thread] Current Thread [Next in Thread]