04:07 <discocaml> <leviroth> I mean. In that specific case the compiler (going by the Godbolt default) doesn't allocate anything in the first place. It just compiles to `movl $3, %eax; ret`

10:43 <discocaml> <muqiuhan> I want to Marshal a `Core.Hashtbl`，I use `Core.In_channel.with_file` with `Marshal.to_channel` to write it to a file, and then read it out in a new utop session using `Marshal.from_channel`，Everything is OK. But when I do the same thing in the file I get an error, why?

10:43 <discocaml> <muqiuhan>

10:43 <discocaml> <muqiuhan> My environment is: x64-linux ocaml-5.2.1

10:43 <discocaml> <muqiuhan> https://cdn.discordapp.com/attachments/436568060288172044/1318528876581752872/image.png?ex=6762a735&is=676155b5&hm=24a3585088e0fabcaffa46a4e5c54b85c7ff5edd4af188189dc2fc980a13593c&

10:43 <discocaml> <muqiuhan> https://cdn.discordapp.com/attachments/436568060288172044/1318528877089394718/image.png?ex=6762a735&is=676155b5&hm=38cbda93a460fe355a3b446fe761488740b76ffa59b4246da658ab1951aaac68&

10:43 <discocaml> <muqiuhan> https://cdn.discordapp.com/attachments/436568060288172044/1318528877445779456/image.png?ex=6762a735&is=676155b5&hm=e8c6399ace9b36c1926f1f76b036899eb0a7a4bbce2c001c6f316c76fd13ef1d&

11:07 <discocaml> <otini_> Presumably marshaling a Core hash table implies marshalling functions, and reading back functions can only be done in the same process or in a process running exactly the same program

11:07 <discocaml> <otini_> > If flags does not contain Marshal.Closures, marshaling fails when it encounters a functional value inside v: only 'pure' data structures, containing neither functions nor objects, can safely be transmitted between different programs. If flags contains Marshal.Closures, functional values will be marshaled as a the position in the code of the program together with the values corresponding to the free variables captured in the closure. In this c

11:13 <discocaml> <muqiuhan> oh

11:15 <discocaml> <otini_> it would work if you ran the same program twice with different command line arguments to select the behavior for instance. But I don’t recommend using Marshal for more than prototyping.

11:36 <discocaml> <muqiuhan> yeah, and i found some other solutions: https://discuss.ocaml.org/t/core-kernel-hashtbl-binable-example/5187/4

17:10 <discocaml> <deepspacejohn> I assume the GC doesn't see any difference between `let foo () = let module M = struct let x = 1 end in M.x` and `let foo () = let r = { x = 1 } in r.x`?

17:10 <discocaml> <deepspacejohn> (RE: the GC and module conversation earlier)

17:18 <discocaml> <octachron> Indeed, modules and functors are records and functions once the typechecking phase is done.

17:32 <discocaml> <otini_> typing-wise, they are :p

17:33 <Anarchos> but i never grasp how the linker works with .cmo / .cmi files

22:20 <discocaml> <functionalprogramming> @aantron does Dream interact with / have anything to do with / have support for server-sent events?

23:26 <discocaml> <yawaramin> see https://aantron.github.io/dream/#val-stream