10:02 <olle> Eyy there's a compiler channel on ocaml discord

10:02 <olle> Didn't know

10:54 <Leonidas> There is no Format-equivalent of Printf.bprintf, is there?

10:56 <Armael> I think you can create a formatter that outputs to a buffer

10:56 <Armael> Format.formatter_of_buffer

10:57 <Leonidas> Yeah, that's an option :-)

10:57 <Armael> TIL Format.str_formatter

10:57 <Armael> which outputs to Format.stdbuf

12:29 <companion_cube> Don't use it

12:30 <companion_cube> Globals are bad, mkay?

13:48 <discocaml_> <Kakadu> I recently got into a situation, when I have 'dune build -w' in one tab, and running 'dune exec asdf.exe' in another tab complain about being locked. Is it a recent ~~feature ~~ bug?

14:18 <discocaml_> <emillon> yes, there's now a lock that ensures that no concurrent processes are using `_build` at the same time. In that case you can pass `--no-build` to `dune exec` so that it does not try to acquire the lock (`dune build -w` is running so the executable will be up to date already)

15:00 <discocaml_> <mbacarella> if a bunch of different opam packages share the same github repo, is opam sophisticated enough to only download that repo once?

15:05 <discocaml_> <Kakadu> @emillon thanks!

15:27 <discocaml_> <emillon> @pilothole yes, and you'll see (cached) in the install log

16:07 <discocaml_> <$Gray> what is the best way to learn OCaml?

18:18 <discocaml_> <RegularSpatula> What was the rational behind changing dune’s locking behavior? I see it come up as an issue for many people

18:33 <discocaml_> <emillon> It has always been broken basically. If processes access the files concurrently they can observe inconsistent behavior. It's unfortunate that all accesses are fully broken but we're making the checks more precise. In the future it will also be possible for concurrent commands to request a temporary lock or ask the watch mode process to make a build on behalf of a command for example, so things should get better.

18:37 <discocaml_> <emillon> It has always been broken basically. If processes access the files concurrently they can observe inconsistent behavior. It's unfortunate that all accesses are fully locked but we're making the checks more precise. In the future it will also be possible for concurrent commands to request a temporary lock or ask the watch mode process to make a build on behalf of a command for example, so things should get better.

20:08 <discocaml_> <RegularSpatula> Interesting, thanks for the info

23:28 <discocaml_> <Alistair> How does one minify the output of the js_of_ocaml?

23:30 <discocaml_> <Alistair> Generated js file is like 4 MiB