Re: Moving most initialization to .scm files

[Jean Abou Samra]

Le 05/09/2022 à 19:50, Jonas Hahnfeld a écrit :
> On Sun, 2022-09-04 at 22:38 +0200, Jean Abou Samra wrote:
> > This needs to be done for lots of code in lots of files, so it will be
> > quite a major change to the source even though it is just a straightforward
> > translation.
> I don't like this idea very much just two weeks before branching for a
> new stable release. No matter how "straightforward", I find the risk
> too high that something goes wrong, or that it turns out not to be a
> good idea for some other reason, or that we still find it insufficient
> and an entirely different solution is required...
>
> For me, this also means we should go without !1510 for the release.
> It's unfortunate, but not the end of the world; and I personally think
> it's worse to delay the entire release by weeks / months or even an
> undetermined amount of time.



It's worth noting that moving the initialization to .scm files (or finding
another solution to the startup time problem, probably via some kind of
caching) is not strictly required to get !1510 in. However, in the case
!1510 is done without it, functions defined in the init .ly files won't 
appear
on the backtraces if something goes wrong while running them. For the next
stable release, we could call it good enough to have at least an option
running the user's code with compile, even if it's not done for the
init code.

(As I said on the MR, I have become weary of providing an option to
byte-compile the init code, even for debugging purposes, since it looks
like a maintenance pitfall.)