07:16 <discocaml> <uberpyro181> annotations `[@warning "-8"]` are deep, so if you put the binding operator in a construct with that annotation, then warnings are silenced for the binding operator as well

07:16 <discocaml> <uberpyro181> ```ocaml

07:16 <discocaml> <uberpyro181> utop # let[@warning "-8"] y = let* (Some x) = [Some 1] in [x; x] in y;;

07:16 <discocaml> <uberpyro181> - : int list = [1; 1]

07:16 <discocaml> <uberpyro181> ```

07:17 <discocaml> <uberpyro181> I annotated `let`, but it should work just as well for `fun`, `match`, etc.

07:21 <luc4> Hello! I'm just getting started with dune and I'm trying to port an ocaml project to it. I'm getting a lot of these errors: https://pastebin.com/r5u8wYYi. Anyone who can explain what it means?

09:05 <YuGiOhJCJ> hello, I try to build "ocaml-ctypes", I type "dune build", I see the missing dependency "ounit2", I try to build "ounit2", I see the missing dependency "lwt.unix", I try to build "lwt", I see the missing dependency "ppxlib", I try to build "ppxlib", I see the missing dependency "ocaml-compiler-libs.common", I try to build "ocaml-compiler-libs.common", I see this: " Type Cmo_format.compunit is not compatible with type string", what am I

09:05 <YuGiOhJCJ> doing wrong? I was able to build several packages like this, but here I am stuck

09:25 <YuGiOhJCJ> I found, it's because I was building "ocaml-compiler-libs" 0.12.4 (too old) instead of 0.17.0

16:42 <discocaml> <nrs9044> what kind of principled approaches to parsing code functionally are there?

16:45 <discocaml> <nrs9044> what kinds of principled approaches to parsing code functionally are there?

16:54 <discocaml> <the.smv> hello ocamllers, I'm new to ocaml glad to be in this server

16:54 <discocaml> <yawaramin> https://github.com/inhabitedtype/angstrom

16:56 <discocaml> <nrs9044> ty for link! from what I'm seeing, it's always some notion of parser combinators right? i.e. that's the sort of conceptual framework behind doing parsing in a functional style

16:56 <discocaml> <nrs9044> ty for link! from what I'm seeing, it's always some notion of parser combinators right? i.e. that's sort of the conceptual framework behind doing parsing in a functional style

17:08 <discocaml> <astreamingcomesacrossthesky> I guess this is typically more of a kind of parsing than a syntactic convention but PEG parsers that I have seen often have a functional style

17:09 <discocaml> <astreamingcomesacrossthesky> But the only PEG parsing library I'm aware of in OCaml uses a Menhir style approach

23:52 <dh`> recursive descent parsers are pretty naturally functional; this is where the idea of monads originated

23:53 <dh`> (note that in practice you don't want to use parser combinator libraries in production; but yawaramin and I will apparently never agree and there's no point reopening that argument)