-
Notifications
You must be signed in to change notification settings - Fork 5.6k
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
8327824: Type annotation placed on incorrect array nesting levels #18211
Conversation
👋 Welcome back liach! A progress list of the required criteria for merging this PR into |
I've read your discussion with @cushon in the comment section for the bug and I agree that type annotations on arrays are unintuitive. Welp, we should make sure they are documented correctly. Do you know if there's a test that exercises this particularly surprising bit from Example 10.2-2. Array Variables and Array Types?
If there isn't, we should add it. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I looked into it; that wasn't easy 😅.
7 years ago a seemingly similar bug, https://bugs.openjdk.org/browse/JDK-8068737, was fixed in javac. It's only now that javadoc is catching up.
Your change seems to be correct, but it disrupts the visitor's pattern. On the other hand, maybe keeping the change confined to visitArray
is for the better here.
Here's what's left to be done:
- resolve merge conflicts due to recently integrated 8325433: Type annotations on primitive types are not linked #18179
- add a couple more test cases; for example, the JLS one that I mentioned earlier and maybe extract something from JBS-8068737
Thanks for doing it.
…rray-anno-order
Thanks for this! The changes look good to me overall. |
…when new members are added
Now fixed merge conflict and added a test case for JLS 10.2-2, with the 2 styles of declarations present in the parameter and the return type respectively. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This PR passes our CI and looks good; thanks.
String @ArrA [] @ArrB [] @ArrC [] @ArrD [] array4() { return null; } | ||
@ArrA ArrParameterized<@ArrC String @ArrA [] @ArrB []> @ArrC [] @ArrD [] manyNested() { return null; } | ||
void varargs(@ArrA String @ArrB [] @ArrC [] @ArrD ... arg) {} | ||
int @ArrA [] mixedStyles(int @ArrB [] @ArrA [] arg) @ArrB [] { return null; } // JLS example 10.2-2 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Took me a second or so to remind myself that this is a valid method declaration with the return type int[][]
:
int[] mixedStyles(int[][] arg) []
@liach This change now passes all automated pre-integration checks. ℹ️ This project also has non-automated pre-integration requirements. Please see the file CONTRIBUTING.md for details. After integration, the commit message for the final commit will be:
You can use pull request commands such as /summary, /contributor and /issue to adjust it as needed. At the time when this comment was updated there had been 15 new commits pushed to the
As there are no conflicts, your changes will automatically be rebased on top of these commits when integrating. If you prefer to avoid this automatic rebasing, please check the documentation for the /integrate command for further details. As you do not have Committer status in this project an existing Committer must agree to sponsor your change. Possible candidates are the reviewers of this PR (@pavelrappo) but any other Committer may sponsor as well. ➡️ To flag this PR as ready for integration with the above commit message, type |
/integrate |
/sponsor |
Going to push as commit 35b00e6.
Your commit was automatically rebased without conflicts. |
@pavelrappo @liach Pushed as commit 35b00e6. 💡 You may see a message that your pull request was closed with unmerged commits. This can be safely ignored. |
Please review this patch that fixes placement of type annotations on array types in Javadoc output. This oversight seems to have existed since JDK 8 but was never noticed or reported.
Progress
Issue
Reviewers
Reviewing
Using
git
Checkout this PR locally:
$ git fetch https://git.openjdk.org/jdk.git pull/18211/head:pull/18211
$ git checkout pull/18211
Update a local copy of the PR:
$ git checkout pull/18211
$ git pull https://git.openjdk.org/jdk.git pull/18211/head
Using Skara CLI tools
Checkout this PR locally:
$ git pr checkout 18211
View PR using the GUI difftool:
$ git pr show -t 18211
Using diff file
Download this PR as a diff file:
https://git.openjdk.org/jdk/pull/18211.diff
Webrev
Link to Webrev Comment