Samuel Mimram

The first is time spent in the function and the second self time I think (the self-time is the time really spent in the function, excluding calls to subfunctions).

I think the best abstraction would be a `select` operator such that ``` select(f, l) ``` with - `f` of type `unit -> int` - `l` of type `source list`...

The situation has been much improved by #3115.

Can you show us the startup times? For instance here: ``` $ ./liquidsoap 'output.dummy(sine())' 2023/11/15 13:42:22 >>> LOG START ... 2023/11/15 13:42:22 [startup:3] DSSI plugins registration: 0.01s 2023/11/15 13:42:22 [startup:3]...

Is `automake` installed on you system?

I am pretty sure that we had proper support for this back in the time and it got broken at some point. Isn't it the case?

I have added an `mli` file (this is better than `private` I think). I cannot put syncLazy as a separate module because some public libraries (e.g. `liquidsoap_lang`) depend on it...

It looks nice, but I am afraid about readability: can you show examples of types functions with many variables (e.g. `ffmpeg.filter.audio_video.output`), is it still readable?...

I don't find this particularly readable... Given that we have many universal variables, can we think of some shorter syntax?

The script ``` s = video.testsrc() output.graphics(s) output.file(%avi, "/tmp/test.avi", s) ``` works well here: https://github.com/savonet/liquidsoap/assets/2012073/176a0b88-2a6b-4617-8f0a-2f33d8c32e88 Could you try to have a simple repro case (which possibly does not involve ffmpeg...