ppx_deriving

Format is part of OCaml stdlib. You can write formatters for it manually. Derivers are a library yes, it's pretty widespread if you need derive functionality, and it can derive basic functions. Proper link: https://github.com/ocaml-ppx/ppx_deriving?tab=readme-ov-file...

> there is no equivalent to Java's toString or Rust's #[derive(Debug)] There are devivers and a Format module for pretty printing. https://github.com/ocaml-ppx/ppx_deriving https://ocaml.org/manual/5.4/api/Format.html

For printing, there’s show in ppx_deriving [1], and I think ppx in general had made my overall experience with OCaml a lot better. [1] https://github.com/ocaml-ppx/ppx_deriving

> You gave a beautiful answer about programming language You do the same thing as in Rust, Scala or Haskell and derive the printer [1]. Then at the callsite, if you know the type then you do `T.show` to print it or `T.eq`. If you don't know the type, then you pass it in at the top level as a module and then do `T.show` or `T.eq`. > Or to convert one type into another type? If you want to convert a type, then you have a type that you want to convert from such as foo and bar, then you do `Foo.to_bar value`. We can keep going, but you can get the point. You _can't_ judge a language by doing what you want to do with one language in another. If I judge Rust by writing recursive data structures and complaining about performance and verbosity that's not particularly fair correct? I can't say that Dart is terrible for desktop because I can't use

Not great, not terrible; the language supports annotations which mean nothing to the compiler but which pre-processors can take advantage of, and there is a framework called ppx which you can use to write your own preprocessor. There exist many pre-processors to do things like add inline tests, generate getter/setter/pretty-printing functions, and so on. Here is an example: https://github.com/ocaml-ppx/ppx_deriving

>The fact that there isn't even a client for the world's most popular search database is indicative of the ecosystem as a whole. It indicates that you haven't written one? That's a rather strange attitude, for sure it doesn't have a wrapper for any rest api, what it has is all needed tools for write it, that's what really matters. The tool in repo above does not even use a library, only generated bindings. It's much easier to write a client to a rest api in OCaml than in Go due to derivers [1], atdgen [2] and the power of the language. Take a look at graphql bindings as an example [3] [4]. [1] https://github.com/ocaml-ppx/ppx_deriving [2] https://github.com/mjambon/atd [3] https://github.com/andreas/ocaml-graphql-server [4] https://www.youtube.com/watch?v=jaKcEGkItsY