03:27 <discocaml> <darrenldl> what's a good choice for fast and stable (at least more stable than marshal) binary serialisation these days in ocaml land?

03:27 <discocaml> <darrenldl> primarily want very fast unpacking

03:48 <discocaml> <yawaramin> anything with a schema should unpack pretty quickly, right? because it won't have to read any field names

04:33 <discocaml> <darrenldl> yeah true, but i want to be lazy and pick something well supported/finished

04:34 <discocaml> <darrenldl> ugh ocamlwiki dot com is flooding my search results again in duckduckgo. anyway.

06:32 <discocaml> <timmcgilchrist> Protobufs has been decent so far. There’s two main libraries for it in OCaml. I’m using it for serializing program backtraces and logging data.

07:37 <discocaml> <davesnx> Hi, we are live in Sabine's stream with fun-OCaml: https://www.twitch.tv/sabine_ocaml

07:37 <discocaml> <davesnx> https://fun-ocaml.com

07:52 <discocaml> <darrenldl> might give protobuf a shot, cheers

10:17 <discocaml> <0x28west> Hello, Everyone

15:15 <discocaml> <0x28west> Ocaml is very hard to install, lot of things to download 😢 I've been trying for 5 hours now

15:22 <discocaml> <._null._> You should only have to download opam manually

16:42 <discocaml> <0x28west> ```ocaml

16:42 <discocaml> <0x28west> Applying: Diskuv ocaml host patch ocaml-common-4_14-a05-msvccflags.patch

16:42 <discocaml> <0x28west> patches(flexdll host) =

16:42 <discocaml> <0x28west> warning: database file for 'clangarm64' does not exist (use '-Sy' to download)

16:42 <discocaml> <0x28west> warning: Public keyring not found; have you run 'pacman-key --init'?

16:42 <discocaml> <0x28west> error: mingw32: key "5F944B027F7FE2091985AA2EFA11531AA0AA7F57" is unknown

16:42 <discocaml> <0x28west> error: keyring is not writable

16:42 <discocaml> <0x28west> error: mingw64: key "5F944B027F7FE2091985AA2EFA11531AA0AA7F57" is unknown

16:42 <discocaml> <0x28west> error: keyring is not writable

16:42 <discocaml> <0x28west> error: keyring is not writable

16:42 <discocaml> <0x28west> [2024-09-16T16:37:02+00:00] share/dkml/repro/100co/vendor/dkml-compiler/src/r-c-ocaml-2-build_host-noargs.sh

16:42 <discocaml> <0x28west> [ERROR:VsDevCmd.bat] *** VsDevCmd.bat encountered errors. Environment may be incomplete and/or incorrect. ***

16:42 <discocaml> <0x28west> [ERROR:VsDevCmd.bat] In an uninitialized command prompt, please 'set VSCMD_DEBUG=[value]' and then re-run

16:42 <discocaml> <0x28west> [ERROR:VsDevCmd.bat] vsdevcmd.bat [args] for additional details.

16:42 <discocaml> <0x28west> [ERROR:VsDevCmd.bat] Where [value] is:

16:42 <discocaml> <0x28west> [ERROR:VsDevCmd.bat] 1 : basic debug logging

16:42 <discocaml> <0x28west> [ERROR:VsDevCmd.bat] 2 : detailed debug logging

16:42 <discocaml> <0x28west> [ERROR:VsDevCmd.bat] 3 : trace level logging. Redirection of output to a file when using this level is recommended.

16:42 <discocaml> <0x28west> [ERROR:VsDevCmd.bat] Example: set VSCMD_DEBUG=3

16:42 <discocaml> <0x28west> [ERROR:VsDevCmd.bat] vsdevcmd.bat > vsdevcmd.trace.txt 2>&1

16:42 <discocaml> <0x28west> ```

16:42 <discocaml> <0x28west> i'm getting this error when i run `opam init -y` on window i have visual studio build tools 2019/2022 installed with all sdk's installed as well

17:18 <discocaml> <yawaramin> i recommend asking in #windows-support and giving details of exactly what you did. eg, open PowerShell, run commands A, B, C, following instructions on XYZ page. and so on

18:56 <discocaml> <getzapped.> Do recursive modules mess with type visibility? I have a module Env with a type t, and another functor that takes a module of Env's signature, and so a function in that functor takes an Env.t. Env is recursive, so I pass itself to the functor to create a module visible within Env. When I pass a value of type t from Env to the function taking Env.t, the compiler complains about the value being of `type t = <actual type>, but a value was expe

18:56 <discocaml> <getzapped.> Do recursive modules mess with type visibility? I have a module Env with a type t, and another functor that takes a module of Env's signature, and so a function in that functor takes an Env.t. Env is recursive, so I pass itself to the functor to create a module visible within Env. When I pass a value of type t from Env to the function taking Env.t, the compiler complains about the value being of `type t = <actual type of Env.t>, but a value

19:02 <discocaml> <getzapped.> fixed it by the functor taking the actual type instead of the abstract Env.t, and having identity converting functions in Env, but it doesnt make sense to me

19:43 <discocaml> <sim642> I can't exactly imagine what you have and where the problem appears, but I think recursive module definitions do have some limitations. Like type equalities not being available in the middle of recursive module definition, but only after it or something. This might've come up recently on Discuss as well

19:44 <discocaml> <sim642> Maybe this is relevant to you: https://discuss.ocaml.org/t/what-is-an-unsafe-functor/14204/8

19:53 <discocaml> <getzapped.> Thanks for the info. I ended up ditching the functor because I remembered the and keyword existed. The functor became useless when I made them properly recursive, then the compiler led me to the manual page for safe modules