06:48 <discocaml> <xfcisco> does anyone know of a server for the lean programming language ?

06:58 <discocaml> <andreypopp> They have zulip instance, not sure about discord, maybe unofficial

08:34 <discocaml> <lukstafi> Hi! What's the go-to simplest test framework for which `dune test --auto-promote` works?

08:35 <discocaml> <lukstafi> Or if simpler, just `dune test` works?

08:40 <discocaml> <andreypopp> I'd say https://dune.readthedocs.io/en/stable/tests.html#cram-tests and then there's also mdx

08:41 <discocaml> <lukstafi> I guess I found my answer: https://ocaml.org/docs/running-executables-and-tests-with-dune#running-tests (although would be nice if there was also a section in the tutorial).

08:44 <discocaml> <lukstafi> But good that I checked and not went through with the instinctive `(library (inline_tests))`

08:53 <hiddenman> zozozo, hi. regarding local opam repository. i've just cloned https://github.com/ocaml/opam-repository/ and run "opam admin cache ./cache" inside it. anyway, it connects to the github for every package and sync it :(

08:53 <hiddenman> like this: [pgx_lwt.1.0] synchronised (https://github.com/arenadotio/pgx/releases/download/1.0/pgx-1.0.tbz)

08:54 <hiddenman> may be i had to mirror the repo with lfs?

08:57 <hiddenman> no, that didn't help. looks like i have to use opam-bundle and fetch sources of everything and then compile everything :(

08:58 <hiddenman> because each package has it's own repository in the github and its archives

09:46 <zozozo> hiddenman: once you have cloned the repo (and probably only kept the package you're interested in), running `opam admin cache./cache` should download every tarball and put in the cache directory iiuc (hence why it should be a good idea to trim the repo first, else you'll download way too many things), and then afterwards, you can configure the repo to serve tarballs from the downloaded cache (you'll

09:46 <zozozo> probably have to configure your opam to use only your local repository and not the default online one though)

09:48 <hiddenman> zozozo, yes, i understand this (actually, i'm not sure what packages i need, because there are lots of recursive deps). the main problem is that i wanted to create a reproducible build: store everything in my local git, then create a cache from it and use. but realized that cache is made by downloading tar.gz for each package from the internet. of course i can sync all packages and just tar.gz the whole directory, but i want to have more elegant

09:48 <hiddenman> solution ;-)

09:49 <hiddenman> so right now i'm determining the required packages and just create git clones for them. and then will use opam pin add git_url for each package

09:49 <hiddenman> so opam will compile then everytime during the build

09:50 <zozozo> ok, in that case, opam-bundle might be a good solution, as it should create a tarball for you (though the build time might be a bit long)

09:54 <hiddenman> zozozo, yes, that's another solution. might be better, experimenting right now. actually, that's annoying problem with the most of the modern languages nowadays: erlang, python, golang, ocaml, npm, etc. especially golang and npm :) there are thousands of packages all around a world and i have to fetch all of them manually, compile and so on. i'd prefer to have everything in the stdlib :)

09:56 <zozozo> hiddenman: oh actually, you could try https://github.com/tarides/opam-monorepo , which I think should fetch all of your deps and build everything locally

09:57 <zozozo> although that maily (only ?) works with projects that use dune as the build system

09:57 <zozozo> *mainly

09:58 <hiddenman> zozozo, hmm, interesting as well. thank you

10:42 <hiddenman> guys. ocaml-compiler-libs (https://github.com/janestreet/ocaml-compiler-libs) wants "ocaml" {>= "5.2.0"}, but i have 4.13.1. how do i determine what ocaml-compiler-libs version to use so it will be compatible with my ocaml 4.13.1?

10:45 <hiddenman> looks like they added this to the master branch, tags releases do not have this

11:06 <hiddenman> another curious thing is that i have to manually determine the order of the pinned packages. for example, i'm pinning ppxlib and it wants sexplib0. i also have sexplib0 pin, but it goes after ppxlib in my script and opam doesnt know that (of course) and tries to install sexplib0 from the github

11:06 <hiddenman> is there any way to add all pinned packages and only after that start building of them?

12:58 <zozozo> hiddenman: you can "opam pin -n" which will only pin the package and not try to install it

13:12 <hiddenman> zozozo, ok, thank you!

13:20 <hiddenman> i managed to pin everything and compile the required library. so thank you everyone for help

13:21 <hiddenman> the only question i do not understand is conf* packages

13:21 <hiddenman> for example, what is that? https://opam.ocaml.org/packages/conf-libpcre/

13:22 <hiddenman> it links to the ocaml-pcre package which is already pinned and compiled. however, this conf-libpcre is installed somehow from somewhere, looks like this is just metadata, but i'm not sure

13:40 <discocaml> <._null._> conf-* packages are virtual packages for external dependencies, they are nothing but an opam file

13:46 <hiddenman> ah, ok, it will not install anything unexpected

15:08 <discocaml> <'a patate> Is there a specific name for a function doing kind of the inverse of map?

15:08 <discocaml> <'a patate> That is, from a function taking the wrapped type, create a function on the unwrapped type...

15:08 <discocaml> <'a patate> ```ocaml

15:08 <discocaml> <'a patate> val dew: ('a t -> 'b t) -> 'a -> 'b

15:08 <discocaml> <'a patate> (* example with Option.t: *)

15:08 <discocaml> <'a patate> let dew f a = f (Some a) |> Option.get

15:08 <discocaml> <'a patate> ```

15:08 <discocaml> <'a patate> Here I call it dew, because if you rotate it it makes map. Funny.

15:09 <discocaml> <'a patate> (yes, I know it can throw an exception, shhh 🤫 )

15:09 <companion_cube> but it's not always correct, right?

15:10 <companion_cube> yeah

15:10 <discocaml> <'a patate> right

15:11 <discocaml> <'a patate> In my special case, it will always be correct

15:16 <discocaml> <'a patate> something like this:

15:16 <discocaml> <'a patate> ```ocaml

15:16 <discocaml> <'a patate> type 'a t = 'a * some_irrelevant_data

15:16 <discocaml> <'a patate> let dew f a = f (a, dont_care) |> fst

15:16 <discocaml> <'a patate> ```

15:17 <companion_cube> ah but it's not the same as iwth option :p

15:18 <discocaml> <'a patate> Why so?

15:18 <companion_cube> because you literally always have a single `'a`

15:19 <companion_cube> not sure what the right concept for that would be though

15:23 <discocaml> <'a patate> Oh yes, on some types you would have to "cheat" a little...