01:46 <cedb> hi, currenty learning, doing a toy project, im trying to wrap my head around the ocolor package. it uses these semantic tags for formatting e.g. Ocolor_format.printf "@{<bold>boldtext@}" lorem, but if I bind that string first instead of passing it literally i get a type error

01:46 <cedb> tyrying to wrap my head how that even makes sense before even understanding the type error itself

01:47 <discocaml> <Kali> that is because string syntax is overloaded to also be format syntax depending on the context it's in

01:49 <discocaml> <Kali> this is why we have can have type-safe printf

01:49 <discocaml> <Kali> and such

01:49 <discocaml> <Kali> because it's not actually a string, it's a formatting literal

01:53 <discocaml> <Kali> by default, they are assumed to be strings, so in your case the binding without a type annotation makes it be a string

01:54 <discocaml> <Kali> which is then a type error since strings and formatters are not interchangable

01:56 <cedb> ah okay that makes sense thanks, so the type of that "syntactic string" would be a Format.formatter object?

01:57 <cedb> ehh, shouldnt use that word

02:00 <cedb> gdmnit didnt expect to fall that fast in the whole pp rabbit hole

02:01 <cedb> can i just annotate the binding to some fixed type just factor out that nasty long string im gonna write

02:06 <discocaml> <Kali> : _ format

02:08 <discocaml> <Kali> let test : _ format = "hello %s"

02:08 <discocaml> <Kali> for instance

02:10 <discocaml> <absolutemillow> i would like to write a lsp in ocaml somehave documentation ?

02:10 <cedb> great thanks

02:11 <cedb> (just found this blog post) http://gallium.inria.fr/blog/format6/ pretty intense thing to have so, idk how to say, close to casual user/newbie surface of interaction

02:11 <cedb> cool, but intense

10:09 <rustyne> Anarchos, adrien: There will be a talk on picos tomorrow at the OCaml workshop (it will streamed)

10:39 <reynir> ^ specifically at 14:00 CEST

11:43 <Anarchos> rustyne

11:43 <Anarchos> ok

15:00 <discocaml> <reynir1396> how do you print the ppx'ed source? I know dune creates a file foo.pp.ml which is a "OCaml abstract syntax tree implementation file" but I forgot how to make that into something readable

15:08 <discocaml> <anmonteiro> if you're using dune you can use `dune describe pp ./path/to/foo.ml`

15:24 <discocaml> <reynir1396> ah great thanks

16:39 <discocaml> <sim642> Maybe the VSCode plugin should just unmarshal and pretty print it, assuming it's self-contained

17:02 <rustyne> `dune show pp ...` works too

18:44 <companion_cube> I'm confused again by deriving_inline

18:44 <companion_cube> there's barely any docs on the subject :/