[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: cl-lib warnings
From: |
Eli Zaretskii |
Subject: |
Re: cl-lib warnings |
Date: |
Wed, 21 Dec 2022 19:14:44 +0200 |
> From: Juanma Barranquero <lekktu@gmail.com>
> Date: Wed, 21 Dec 2022 15:50:52 +0100
> Cc: João Távora <joaotavora@gmail.com>, juri@linkov.net,
> monnier@iro.umontreal.ca, emacs-devel@gnu.org
>
> On Wed, Dec 21, 2022 at 3:22 PM Eli Zaretskii <eliz@gnu.org> wrote:
>
> > Our policy and practice was since long ago that any package which is
> > always or almost always loaded at startup without any user say-so,
> > should be preloaded, since not doing that makes very little sense.
>
> We don't have precise metrics for "always or almost always loaded at
> startup", I think.
"Always" doesn't require any metrics.
> But cl-lib is unconditionally required by 191 files under lisp/,
> right now.
Out of 1600+, yes.
- Re: cl-lib warnings, (continued)
- Re: cl-lib warnings, João Távora, 2022/12/21
- Re: cl-lib warnings, Juanma Barranquero, 2022/12/21
- Re: cl-lib warnings, João Távora, 2022/12/21
- Re: cl-lib warnings, Milan Glacier, 2022/12/25
- Re: cl-lib warnings, João Távora, 2022/12/26
- Re: cl-lib warnings, Milan Glacier, 2022/12/26
- Re: cl-lib warnings, João Távora, 2022/12/26
- Re: cl-lib warnings, Tim Cross, 2022/12/26
- Re: cl-lib warnings, Lynn Winebarger, 2022/12/27
- Re: cl-lib warnings, Stefan Kangas, 2022/12/27
- Re: cl-lib warnings,
Eli Zaretskii <=
- Re: cl-lib warnings, Juanma Barranquero, 2022/12/21
- Re: cl-lib warnings, Eli Zaretskii, 2022/12/22
- Re: cl-lib warnings, Juanma Barranquero, 2022/12/22
- Re: cl-lib warnings, Eli Zaretskii, 2022/12/22
- Re: cl-lib warnings, Yuan Fu, 2022/12/22
- Re: cl-lib warnings, Stefan Monnier, 2022/12/22
- Re: cl-lib warnings, Eli Zaretskii, 2022/12/23
- Re: cl-lib warnings, Yuan Fu, 2022/12/23
- Re: cl-lib warnings, Juanma Barranquero, 2022/12/23
- Re: cl-lib warnings, Stefan Monnier, 2022/12/24