10:55 <discocaml> <leostera> hi everyone 👋 the OCaml Build System team at Tarides is looking to get inputs from all of you to improve the Dune DX (developer experience), so we've opened a short, anonymous, unstructured feedback form (https://forms.gle/brutt9hD8SVbzP1T9) to hear your ideas on how Dune could be improved!🐫

10:55 <discocaml> <leostera>

10:55 <discocaml> <leostera> we're looking forward to your ideas! ✨

10:59 <olle> How to run a single test with Dune, and not the entire test suite?

11:00 <olle> One of those things that are trivial in other systems ;)

11:10 <discocaml> <lroche> Tests in ocaml? But the code always works! 🙂

11:15 <olle> Hehehe

11:15 <olle> Not my code, it doesn't xD

13:05 <discocaml> <deepspacejohn> depending on how your tests are implemented, it can be simple. if they're just executables (e.g. with Alcotest) then just run that executable: `dune exec tests/my_test.exe`. If they're cram tests then Dune automatically adds aliases for them: `dune build @my-cram-test`. If they're something else then you may just have to add your own aliases.

13:05 <discocaml> <deepspacejohn> see also https://github.com/ocaml/dune/issues/10239

13:27 <discocaml> <lukstafi> On top of that, you can split tests into directories and run a specified directory tests only.

13:29 <discocaml> <lukstafi> Inline tests are automatically added to the `runtest` alias, performed by `dune test`. To run just a directory `tests1`, `dune test tests1`

13:31 <discocaml> <deepspacejohn> I do agree that the way Dune abstracts the concept of tests feels inconsistent and could definitely be improved. The fact that a "test" could be so many different things gets confusing.

14:02 <discocaml> <lukstafi> It's impossible to have inline tests that don't get run by `dune test` or `dune build @runtest`, but it's also impossible to not pass `dune build ... @runtest {with-test}` to the opam file...

15:01 <anadon> leostera: I got you :)

15:10 <discocaml> <lukstafi> It's impossible to have inline tests that don't get run by `dune test` or `dune build @runtest`, but it's also impossible to not pass `dune build ... @runtest {with-test}` to the opam file... Edit: but I learned I can just rewrite the opam file that's sent to opam-repository.

15:35 <discocaml> <mimi_baboon> Hey! Is there any good ocaml bindings for https://pytorch.org/docs/stable/distributed.html ?

16:44 <mccd> Hey, should I be using cohttp or httpaf?

16:44 <mccd> for a minimal web server

17:44 <discocaml> <regularspatula> There are a couple of PyTorch bindings…not sure if they have that particular module though

17:52 <discocaml> <yawaramin> try Dream

18:54 <discocaml> <Alistair> Dream uses httpaf, if they want minimal then they should likely use cohttp or httpaf

18:55 <discocaml> <Alistair> I personally use cohttp for most of my stuff

19:39 <discocaml> <leostera> +1 to recommend high level libraries for minimal stuff

19:39 <discocaml> <leostera> low-level libs should remain hidden

19:43 <discocaml> <leostera> +1 to recommending high level libraries for minimal stuff

19:44 <discocaml> <yawaramin> also, 'minimal' is subjective, people would define it differently, eg many would say Dream is minimal because it doesn't come with an ORM or a job queueing system

19:44 <discocaml> <leostera> right! minimal is not always "low-level"

19:45 <discocaml> <leostera> to me minimal in this case is more about a small lib that lets me do what i want with the least amount of noise/boilerplate

19:45 <discocaml> <leostera> and yes dream has a bunch of stuff that goes beyond the router+controller combo, but you don't have to use it all

19:46 <discocaml> <leostera> (also i know you know yawar :P, so i'm mostly writing for other folks here in chat that maybe see dream as this big rails like monolithic framework)

21:43 <anadon> I'm unpacking a vertex as a part of walking a tree. I'm doing so using functions like "let program' cst = match cst with | program_ located -> [ program program_ ] ". No idea if the syntax is right yet. Is this how I should be walking the tree?

22:17 <discocaml> <Kali> "*" is the tuple type constructor, "," is the tuple value constructor

22:18 <discocaml> <Kali> wait, nevermind, discord formatting

22:18 <discocaml> <Kali> disregard that message