08:23 <discocaml> <jordan4ibanez> So ocaml huh

08:24 <discocaml> <jordan4ibanez> A modern multi paradigm ml?

08:24 <discocaml> <jordan4ibanez> Oh wait this is the wrong channel lmao

10:24 <neiluj> hey! I'm trying to build a library using flambda 2 but I get the following error when compiling dependencies for Core: https://bpa.st/CKXQ

10:25 <neiluj> do you have an idea what's going on?

11:32 <type> Hi. Are there any alternatives to Core's Sys_unix.command that allows me to use the outputs of an external program before it finishes executing? Specifically, I need to execute an external program and then incrementally feed inputs to it using the standard input. For each of these inputs, the external program will react and output something, which

11:32 <type> I would like to consider in my OCaml program.

11:38 <discocaml> <drupyog> containers has a function that does that

11:43 <type> Are you referring to CCUnix.call?

12:06 <discocaml> <jordan4ibanez> You can get literally live output of what you're doing to your terminal with how fast this compiles, this is incredible

12:13 <discocaml> <leviroth> type: Unix.open_process_in?

12:14 <discocaml> <leviroth> There is also a core-flavored version in Core_unix if you prefer

12:34 <discocaml> <romain.beauxis> Hey there! I'm doing some memory consumption analysis on a ocaml program with a fairly large code base and dependencies. Do y'all know if there is a way/a tool to measure how much each module or ocaml library contributes to the program and potentially its memory usage.

12:34 <discocaml> <romain.beauxis> So far it seems that the larger the binary, the more memory usage even if the program doesn't do much. This also increases CPU usage.

12:35 <discocaml> <darrenldl> that seems difficult when things are passed between modules

12:35 <discocaml> <darrenldl> do you happen to be on 5.1?

12:35 <discocaml> <romain.beauxis> No, also for memory consumption issues.

12:35 <discocaml> <darrenldl> oh right i also read ur text not quite correctly. hmm

12:37 <discocaml> <romain.beauxis> No worries it's a mouthful. I'm also wondering if the possibility of having the compiled code be loaded as shared memory has ever been studied. So far it seems that the program's code lives as private memory which seems unfortunate.