03:36 <discocaml> <struktured> companion_cube: got it working but the only difference between then and now is I didn't use the bistro command and instead invoked each step separately.

03:37 <companion_cube> only way I use it

03:37 <discocaml> <struktured> good call on that, it's not like it's a big deal to run 4 or 5 commands

13:41 <darchitect> hey guys, I have programmed a tiny bit in OCaml before (mainly doing leetcode problems) and want to learn the language properly, but I saw that OCaml 5 was released recently and was wondering whether anyone here knows some books for a beginner to get started which also cover ocaml 5. I have seen real world ocaml, but I don't know which parts are still relevant ?

13:44 <octachron> The "only" difference between OCaml 5 and OCaml 4 are the support for shared memory parallelism and algebraic effects. So only new features, and too recent to have completely displaced any pre-existing libraries yet.

13:45 <octachron> In other words, outside of those new features, you can pick any documentation for OCaml 4 and will still apply to OCaml 5.

13:49 <discocaml> <lukstafi> https://ocaml.org/docs gives a great overview. Depending on your learning style, the manual https://v2.ocaml.org/releases/5.1/htmlman/index.html might be for you, it combines tutorial parts with dry / formal / completeness parts.

13:51 <darchitect> thanks, I guess I will stick with the real world ocaml book

13:51 <darchitect> for the time being

13:51 <darchitect> there is a chapter on Async, do you think I should skip that and find other sources ?

14:02 <octachron> Potentially, but the replacement for Async/lwt is still very much in flux

16:50 <discocaml> <diligentclerk> Can you denote the Cartesian product of types `'a, 'b` by `('a, 'b)`

16:51 <discocaml> <octachron> No, at the type level the product is `'a * 'b`.

16:51 <discocaml> <octachron> (In OCaml at least)

16:51 <discocaml> <diligentclerk> I am reading someone's module signature and they write

16:51 <discocaml> <diligentclerk> ```ocaml

16:51 <discocaml> <diligentclerk>

16:51 <discocaml> <diligentclerk> (** Entry point: two *)

16:51 <discocaml> <diligentclerk> val two: Context.t -> int32 -> int32 -> (int32, int32)

16:51 <discocaml> <diligentclerk>

16:51 <discocaml> <diligentclerk> ```

16:51 <discocaml> <diligentclerk> Is this valid syntax?

16:51 <discocaml> <diligentclerk> Or are they mixing it up with another language

16:52 <discocaml> <octachron> this is not a valid vanilla syntax

16:52 <discocaml> <diligentclerk> My IDE gives me an error when i try to load it and Dune spits out ugly garbage.

16:53 <discocaml> <diligentclerk> Ok. This code was generated automatically / procedurally so somebody probably just forgot the syntax for product types when writing the code generator.

16:53 <discocaml> <diligentclerk> i'll file a bug report with the code generator.

17:02 <discocaml> <Ada> i've been using `Result.bind` a lot for unrecoverable errors where i dont want to mix results and exceptions and i feel like in some places it is making my code very ugly

17:09 <discocaml> <deepspacejohn> using binding operators (e.g. `let (let*) = Result.bind`) can help it look prettier

17:45 <discocaml> <Ada> oh cool, i've used bindings extensively with lwt but didn't put two and two together

18:08 <discocaml> <deepspacejohn> They can be used for any function with a compatible signature

20:22 <discocaml> <leostera> hey folks, how do you define a dependency between a dune library and a melange.emit stanza? I'd like to always carry around the generated .js with the library

20:31 <discocaml> <andreypopp> @leostera via dune sites, example https://github.com/andreypopp/react_of_ocaml/blob/91154f6122d80766e851d65e23cf11ab32270715/hx/dune#L96

22:39 <discocaml> <leostera> ended up using a mix of rule+action+ocaml-crunch to pack the js into the executable

22:39 <discocaml> <leostera> but thanks @andreypopp this was useful to arrive to something that worked for me! 🙏🏼

22:40 <companion_cube> in tiny_httpd I have a little asset packer for these use cases

22:41 <companion_cube> and then a rule like this: <https://paste.isomorphis.me/s3Q>

22:51 <discocaml> <leostera> cool! yes that's more or less what i did

22:51 <discocaml> <leostera> just call ocaml-crunch insteaad

22:51 <discocaml> <leostera> just call ocaml-crunch instead

22:52 <discocaml> <leostera> i'd love to hear from other folks on how thye're packaging their releases when they have several assets and config files (potentially that need to be outisde the app to allow users to configure them)