-
Notifications
You must be signed in to change notification settings - Fork 139
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
Adding kind for node[] fields where possible #2058
Comments
eregon
changed the title
Adding kind for node[] fields
Adding kind for node[] fields where possible
Dec 13, 2023
Yes I agree. I think we should also use this opportunity to expand the syntax to support a set of nodes for languages where a union makes sense. |
Indeed, a union would be super helpful, even if it only ends up in documentation. |
Probably we can consider this done when #2101 (comment) is merged. |
eregon
added a commit
to eregon/yarp
that referenced
this issue
Feb 25, 2024
…n "any Node" * Fixes ruby#2058
eregon
added a commit
to eregon/yarp
that referenced
this issue
Feb 25, 2024
…n "any Node" * Fixes ruby#2058
eregon
added a commit
to eregon/yarp
that referenced
this issue
Feb 28, 2024
…n "any Node" * Fixes ruby#2058
matzbot
pushed a commit
to ruby/ruby
that referenced
this issue
Feb 28, 2024
… specific than "any Node" * Fixes ruby/prism#2058 ruby/prism@f3e3310b5e
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
For at least some of the node[] we could give a kind and so that array's elements would have a proper type in documentation, Java code, etc.
Some example:
Some counter example:
In some cases it's not possible because multiple classes are possible, or a MissingNode is possible.
The text was updated successfully, but these errors were encountered: