00:10 <dh`> is it? it's a separate package in my world, and a separate source distfile

00:13 <twobitsprite> dh`: every other SDL language binding I've used included IMG. Are you here to be helpful, or are you just here to get dopamine hits by being a snarky know-it-all?

00:33 <dh`> huh?

00:34 <dh`> well excuse me, just trying to suggest reasons why it might not be there

00:34 <dh`> sheesh

04:28 <discocaml> <.armael.> https://github.com/tokenrove/tsdl-image ?

04:28 <discocaml> <.armael.> it should be in opam as well

11:42 <discocaml> <gooby_clown> Do we have to fill in dune-project with all the dependencies scattered throughout the dune files manually, or is there a way for dune to fill them in on its own

11:42 <discocaml> <gooby_clown> Would be great if it was like npm where installing also adds it to the project dependencies

11:59 <discocaml> <deepspacejohn> If I export a type that uses types from a functor, is there a simpler way to specify them in the interface than `type foo = { bar : int Map.Make(String).t }`?

12:00 <discocaml> <deepspacejohn> In other words, is there a way to "alias" the result of `Map.Make(String)` and reuse it in the interface, without actually having to export that module?

12:02 <discocaml> <deepspacejohn> @Gooby I don't think so. Technically, you don't need to specify them in dune-project at all. Dune is pretty agnostic as to how you manage your dependencies. I think putting them in dune-project is just for if you use Dune to generate opam files.

12:03 <discocaml> <deepspacejohn> @gooby_clown I don't think so. Technically, you don't need to specify them in dune-project at all. Dune is pretty agnostic as to how you manage your dependencies. I think putting them in dune-project is just for if you use Dune to generate opam files.

12:14 <discocaml> <gooby_clown> I do use it to generate the opam file, but what I actually want to do is to be able to, after cloning my own project, be able to run a single command to install the dependencies in the current switch. Opam has `opam install --deps-only` but for that the deps need to be in the opam file, and with generated opam files that means them being in the dune-project, so I was thinking how it would be nice if dune could populate that by itself by ju

12:27 <discocaml> <deepspacejohn> Yeah, I don’t think there’s a way to completely automate it. Maybe whenever Dune releases its own packaging management feature it might be easier.

12:33 <discocaml> <ada2k> library names are different from opam packages anyway

12:40 <discocaml> <leviroth> Good point

12:44 <discocaml> <ada2k> i don’t find it that much of a hassle anyway, if i have lots and lots of dependencies it’s normally broke up into a couple of packages that depend on each other

12:45 <discocaml> <ada2k> having dune say discern from (libraries logs.fmt) that you want to depend on logs and fmt would need a mini solver

13:00 <discocaml> <deepspacejohn> Yeah, I don’t really mind it much either. Theoretically it would be nicer to automate things more but also OCaml projects don’t have a gazillion dependencies like npm projects do

13:32 <discocaml> <gooby_clown> Fair fair, I see

13:46 <discocaml> <leviroth> Is it not the case that you can unambiguously map findlib names to file paths, and file paths to opam packages?

15:08 <discocaml> <ada2k> i'm sure you can, it would just be a PITA.

15:46 <discocaml> <davesnx> did anyone implemented an async JSON parsing lib?

15:52 <discocaml> <deepspacejohn> jsonm works with streaming data, if that fits what you want

16:03 <discocaml> <davesnx> thanks, that's what I was looking for

16:10 <companion_cube> Can you work around that by using jsonl or sth reasonable of that sort?

16:50 <discocaml> <davesnx> I didn't know jsonl !!!!

16:51 <discocaml> <davesnx> but in this case I need json 😦

16:58 <discocaml> <getzapped.> are jane street's rust-style ownership extensions available to use or are they more like propositions yet to be implemented?

17:10 <companion_cube> @davesnx sorry for your situation :p

17:53 <discocaml> <davesnx> hahaha

19:15 <twobitsprite> I just tried to run "opam install tsdl-image" in my linux vbox VM, and it just hang, maxing out all 4 of my system's CPU cores......

19:15 <twobitsprite> I had to kill the VM and reboot it

19:16 <twobitsprite> running it again, it seems to be happy now, idk what happened

19:40 <twobitsprite> anyway..... I got tsld_image installed, added it to my (depeneds ...) stanza in my dune-project file, and in the (libraries ...) stanza in my lib/dune file, but I'm getting: Error: Library "tsdl_image" not found.

19:43 <discocaml> <Kali> did you install it

19:43 <discocaml> <Kali> dune build; opam install . --deps-only

19:44 <discocaml> <Kali> dune doesn't install anything, it just generates the file to install from

19:44 <discocaml> <Kali> wait, nevermind

19:44 <twobitsprite> kali: yes, I did "opam install tsdl_image"

19:44 <discocaml> <Kali> i didn't read the first part of the sentence 😅

19:44 <twobitsprite> :P

19:47 <twobitsprite> I just pushed what I have to github, if you want to look it over: https://github.com/memotype/olarn

19:50 <discocaml> <Kali> well first off tsdl and tsdl-image are separate packages but you only have tsdl in (depends ...) it seems

19:50 <twobitsprite> (depends ocaml dune tsdl tsdl_image)

19:51 <discocaml> <Kali> it doesn't show that for me

19:51 <twobitsprite> ohhh, sec

19:51 <twobitsprite> https://github.com/memotype/olarn/tree/test

19:51 <twobitsprite> test branch, sorry

19:51 <discocaml> <Kali> also it's tsdl-image (hyphen) not tsdl_image (underscore)

19:51 <twobitsprite> even in the lib/dune file?

19:52 <twobitsprite> ahh, that fixed it, thanks

19:52 <discocaml> <Kali> try changing that and see if it fixes it

19:52 <discocaml> <Kali> yeah

19:52 <discocaml> <Kali> hyphens and underscores aren't interchangeable

19:52 <twobitsprite> it's a bit confusing that in ocaml-land, it's _, but in opam- and dune-land it's - ...

19:53 <discocaml> <Kali> yeah

19:53 <discocaml> <Kali> then you've got some that mix both

19:53 <twobitsprite> anyway, good to know, thanks

19:53 <discocaml> <Kali> js_of_ocaml-ppx

19:58 <twobitsprite> even though it can be frustrating sometimes, it is super satisfying getting that zero output from "dune build" :D

21:53 <discocaml> <ada2k> twobitsprite: it’ll become second nature. wait until you have a project with 10 pin depends

22:10 <discocaml> <ada2k> how involved is the process for submitting an opam package? can dune just do it now

23:15 <companion_cube> Use dune release