14:05 <loopspace> I'm new to dune/opam and I've been trying to grasp appropriate directory structure for a project. I ran through some hello world tutorials, and managed to get lex and yacc working. Next I'm trying to "port" a Makefile-based project over to dune. I've tried a number of structures for several hours, but I don't quite get how to organize the tree without having to change any source files.

14:05 <loopspace> https://www.irccloud.com/pastebin/upvh1aie/

14:06 <loopspace> Any suggestions, particularly with regard to library subdirectory structure would be welcome

14:10 <companion_cube> I'd suggest looking at some popular libraries on opam that use dune, specifically at how they use it

14:10 <companion_cube> In general, one directory per library, with a dune file in it

14:17 <loopspace> thanks, I will try to have a look. My last (partial attempt) looked something like this. https://www.irccloud.com/pastebin/SBXlJwLv/

14:18 <loopspace> My error was: ~/ml/fourth $ dune build

14:18 <loopspace> File "bin/main.ml", line 9, characters 5-22:

14:18 <loopspace> 9 | open Support.Pervasive

14:18 <loopspace> ^^^^^^^^^^^^^^^^^

14:19 <loopspace> where main.ml included the line open Support.Pervasive

14:20 <loopspace> https://www.irccloud.com/pastebin/B6LxUAzN/

14:22 <companion_cube> The first big red flag is: you should have exactly one dune-project, at the root

14:22 <companion_cube> And thus only one _build

14:22 <companion_cube> Here it's like you have separate projects, so they don't know about each other

14:23 <companion_cube> Look at my containers repo for an example if you want :)

14:23 <loopspace> Ah, I see. In my attempts to get rid of that error, I dune init-ed projects for support and syntax. Thanks for steering me away from that error. I will look at containers, thanks

14:27 <companion_cube> 👍

16:24 <loopspace> update: seems that the main impediment was that I needed to use (wrapped false) for the lib in this case (older source code)

22:27 <discocaml> <masterbuilder> is there anything like decltype in Ocaml? i.e. use the type of object A and use that to annotate object B

22:27 <discocaml> <masterbuilder> is there anything like decltype in Ocaml? i.e. get the type/ of object A and use that to annotate object B

23:09 <companion_cube> No, you can't ask for the type of an expression

23:55 <masterbuilder> I see

23:57 <masterbuilder> by the way I noticed that when I wrote `s/<typo>/.../` in Discord for the benefit of the IRC people it resulted in an actual edit of the post, what's up with that? furthermore it was sent to the IRC side as a repeated message, which was exactly what I was trying to avoid. Is it a bot you're experimenting with or is this a new Discord feature?

23:59 <discocaml> <darrenldl> discord recognises a subset of s// replacement syntax