goderive
ppx_deriving
Our great sponsors
goderive | ppx_deriving | |
---|---|---|
3 | 7 | |
1,161 | 439 | |
- | 2.3% | |
2.8 | 7.0 | |
19 days ago | about 21 hours ago | |
Go | OCaml | |
Apache License 2.0 | MIT License |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
goderive
-
Why GoLang supports null references if they are billion dollar mistake?
Now, am I going to do the same with a library like goderive just so I can use FP techniques to get, amongst some other things, less nil checks? No. Probably not. If I wanted to use primarily FP techniques in my code, I would probably be using something else in the first place. Go isn't a great environment for guaranteeing immutability for starters, so anything like that is necessarily going to be an incomplete experience. And in the bargain, my code would, in my opinion at least, be less readable and maintainable.
ppx_deriving
-
My Thoughts on OCaml
> 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 chrome developer tools on its canvas output and ignore it's hot-reloading server. I can't say Common Lisp code is unreadable because I don't have type annotations and ignore the REPL for introspection.
-
Is rust serde unique?
Ocaml has the amazing ppx_deriving which can be used for serialization / deserialization in various formats.
-
Question on type declaration syntax
I wrote a CLI tool and I'd like to produce statically linked binaries of my tool. However, I cannot do this because I'm using the ppx_deriving deriving preprocessor, and I cannot produce a statically linked executable while using this package.
-
OCaml at First Glance
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:
-
Bad documentation of Jane Street libraries
is from https://github.com/ocaml-ppx/ppx_deriving
-
Recommended method for pretty-printing collections in Core?
Have you tried to derive a print function using https://github.com/ocaml-ppx/ppx_deriving
What are some alternatives?
go-enum - An enum generator for go
goverter - Generate type-safe Go converters by simply defining an interface
deriving-show-simple
ppx_jane - Standard Jane Street ppx rewriters
gotype - Golang source code parsing, usage like reflect package
go-xray - Helpers for making the use of reflection easier
GoWrap - GoWrap is a command line tool for generating decorators for Go interfaces
typeregistry - create type dynamically in Golang
generis - Versatile Go code generator.
ppx_sexp_conv - Generation of S-expression conversion functions from type definitions
json-serde - Example of usage antlr4 and shapeless
generic-data - Generic data types in Haskell, utilities for GHC.Generics