-
Notifications
You must be signed in to change notification settings - Fork 42
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Support Proper's Deriving of Types #69
Comments
I am happy to help FWIW |
I don't really understand the issues 3 - 5 you cited. Is there a fundamental problem, or is it just a lot of work? |
Back in time - if I remember right and 3 years is a lot of time - I recognised that parsing/handling of more interesting types in Proper was done on a source code level, ie. there are differences between Erlang and Elixir. To handle this properly means that you need understand the Elixir encoding of types, unparse them to Erlang syntax and after that deal with the undocumented internal type server from Proper. So it is an arbitrary big set of work with a questionable result if you consider the arguments of Jesper Andersen (see the readme). A better approach would be that the internals of PropEr are fixed (i.e. no Erlang syntax for types), but I do not know whether this has ever happened. There are some refactorings in Proper for supporting Targeted PBT, but I did not check the details. Proper is quite complex inside and not for the faint of heart. I won't do it, but I am happy about PRs. But currently I am way more interested in understanding Targeted PBT, its usage patterns and how to provide a stable interface for that in Elixir (my current solution and its tests are flaky). |
I just did a talk on using types in Erlang/ elixir, I am uploading it to youtube as I type this |
I implemented a small library propcheck_derive to derive generators from |
What would be required to be able to derive types as the Erlang implementation does?
The text was updated successfully, but these errors were encountered: