-
Notifications
You must be signed in to change notification settings - Fork 68
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 annotating return types next to rules #101
Comments
@lolbinarycat Thanks for your proposal and sorry for my slow answer. I looked into this idea some time ago. It turned out to be more complicated than I initially thought. But feel free to start with an implementation and open a PR, then we can work on this. |
@breml I originally planned to do just that and open a PR, but I've done a fair bit of work on various parsers, and I'm a bit tired of it for now. I may get back to it sometime though. |
@lolbinarycat Never mind, I leave the issue open for now. |
Duplicate of #62 |
the proposed syntax would be:
where TYPES is anything that is a valid return type for a go function. e.g.
(string,error)
,int16
or even nothing (like infunc main()
).This return type would then be copied exactly to the generated code.
The text was updated successfully, but these errors were encountered: