-
Notifications
You must be signed in to change notification settings - Fork 31
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
Void parameter sets should not require declaration #2
Comments
Can I work on it |
Sure! I would start by looking at class.h and method.h. Also, I don't know what your setup is like, and I wouldn't be surprised if you need to resolve some blockages (i.e. #42). This is obviously gating for 1.0 release, but I may not be able to do much in the immediate term. If you can unblock that, it would be a help. |
I thought it would be easy but now I am not getting what to do |
Basically, i.e. I must write this: Method {"Foo", Return{}, Params{}} when I want to write this: Method {"Foo", Return{}} The task is to write a constructor for |
#2 PiperOrigin-RevId: 618473835
#2 PiperOrigin-RevId: 618473835
#2 PiperOrigin-RevId: 618473835
#2 PiperOrigin-RevId: 618473835
#2 PiperOrigin-RevId: 618891608
I seem to be seeing issues when these classes are being used as return values in chained calls. I'm going to investigate. |
Empty returns, constructors, and methods should not require specification.
The text was updated successfully, but these errors were encountered: