[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Lisp files that load cl-lib in problematical ways
From: |
Eli Zaretskii |
Subject: |
Re: Lisp files that load cl-lib in problematical ways |
Date: |
Tue, 24 Oct 2023 15:54:04 +0300 |
> From: Emanuel Berg <incal@dataswamp.org>
> Date: Tue, 24 Oct 2023 14:43:48 +0200
>
> Eli Zaretskii wrote:
>
> > If we ignore such "micro optimizations", we will quickly
> > bloat Emacs, since those small amounts add up. We have a lot
> > of relatively small potential additions that we make a point
> > of not adding, because if we decide adding one is okay, then
> > why not add all the rest? We don't add such stuff to subr.el
> > or to simple.el or to files.el, and keep them separate,
> > precisely because adding them all will not be insignificant.
> >
> > The only way of keeping this kind of bloat at bay is to
> > resist adding anything, no matter how small, because, like
> > I said, it's a slippery slope.
>
> While I agree one shouldn't ignore micro optimizations in
> general, you keep refering to useful Elisp as bloat.
No, I said that loading stuff that _is_not_necessary_ will _cause_
bloat. Please don't misrepresent what I wrote.
> That is disrespectful and also not true, it is useful code, and
> where it is or isn't added or loaded doesn't change it into
> something it isn't.
See above.
> Also, instead of the general "slippery slope" model of thought
> and offered explanation, it is better to either have a clear
> policy "we add stuff that [...]".
The policy exists and is clear: we don' preload anything that isn't
needed by Emacs either during the dumping process or when it starts
after dumping.
- Re: Lisp files that load cl-lib in problematical ways, (continued)
- Re: Lisp files that load cl-lib in problematical ways, Andrea Corallo, 2023/10/24
- Re: Lisp files that load cl-lib in problematical ways, Corwin Brust, 2023/10/24
- Re: Lisp files that load cl-lib in problematical ways, Andrea Corallo, 2023/10/24
- Re: Lisp files that load cl-lib in problematical ways, Ihor Radchenko, 2023/10/24
- Re: Lisp files that load cl-lib in problematical ways, Corwin Brust, 2023/10/25
- Re: Lisp files that load cl-lib in problematical ways, Eli Zaretskii, 2023/10/24
- Re: Lisp files that load cl-lib in problematical ways, Stefan Kangas, 2023/10/24
- Re: Lisp files that load cl-lib in problematical ways, Björn Bidar, 2023/10/24
- Re: Lisp files that load cl-lib in problematical ways, Eli Zaretskii, 2023/10/24
- Re: Lisp files that load cl-lib in problematical ways, Emanuel Berg, 2023/10/24
- Re: Lisp files that load cl-lib in problematical ways,
Eli Zaretskii <=
- Re: Lisp files that load cl-lib in problematical ways, Emanuel Berg, 2023/10/24
- Re: Lisp files that load cl-lib in problematical ways, Björn Bidar, 2023/10/24
- Re: Lisp files that load cl-lib in problematical ways, Eli Zaretskii, 2023/10/24
- Re: Lisp files that load cl-lib in problematical ways, Emanuel Berg, 2023/10/24
- Re: Lisp files that load cl-lib in problematical ways, Eli Zaretskii, 2023/10/24
- Re: Lisp files that load cl-lib in problematical ways, Richard Stallman, 2023/10/26
- Re: Lisp files that load cl-lib in problematical ways, Eli Zaretskii, 2023/10/27
- Re: Lisp files that load cl-lib in problematical ways, Emanuel Berg, 2023/10/23
- Re: Lisp files that load cl-lib in problematical ways, Björn Bidar, 2023/10/19
- Re: Lisp files that load cl-lib in problematical ways, Richard Stallman, 2023/10/22