-
Notifications
You must be signed in to change notification settings - Fork 10
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
Hydra-Go #65
Comments
Started working on this, on the branch |
TODO: figure out how to represent the following productions:
|
TODO: figure out how to represent keywords:
|
These lexer details are really only important if you intend to use the grammar to generate a parser and/or a serializer for Go. That is the intention of preserving all of the information in the BNF grammar, but so far we haven't tried to generate serializers (e.g. see GraphQL). That would definitely be a worthwhile thing to do for the first time (and would probably require some extension of the hydra/grammar module). |
See |
Leaving this comment as a reminder to myself: I need to set up the simplest possible test case to quickly validate that I'm doing things correctly. I think a good simple case would be to generate a simple integer variable declaration in Go, from a Hydra DSL. |
A partial or even full Go implementation of Hydra is likely to be required for some of our work at LinkedIn. Start by creating a Go model and Go language constraints, then proceed to a type-level Go coder. Extend this to a bicoder if practical, and implement as much of the Hydra kernel as is required for that particular use case. The recent work on migrating the kernel to Java will likely make a Go migration simpler.
The text was updated successfully, but these errors were encountered: