-
Notifications
You must be signed in to change notification settings - Fork 36
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
Ocaml keyword conflicts #24
Comments
Hello - I don't work on Piqi, however I had the same issue. See https://gist.github.com/metadave/3195858 for @alavrik's response. Cheers - |
Take a look at the @metadave's example. There is a very simple and elegant solution to this practical problem. The use of As for the checks, I think it it would be a nice addition to |
Thanks, I like @metadave's example. For me, though, it's just as easy to change the names, because I only use ocaml. I think adding the checks to |
Moving this issue to the newly created piqi-ocaml repo. |
I am using piqi to serialize some language related types. The following type names result in errors when compiling piqi-generated ML code:
I am sure there are more; these are only the ones I ran into. It would probably be a good idea to check for any ocaml keywords and disallow them as type or field names in piqi.
The text was updated successfully, but these errors were encountered: