-
Notifications
You must be signed in to change notification settings - Fork 5.8k
8267633: Clarify documentation of (Doc)TreeScanner #4174
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
Conversation
👋 Welcome back prappo! A progress list of the required criteria for merging this PR into |
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.
OK.
I'm not entirely comfortable with the phrasing of call with
but I understand the issue with call on
.
@@ -39,13 +39,13 @@ | |||
* <ul> | |||
* <li>If the node being visited has no children, the result will be {@code null}. | |||
* <li>If the node being visited has one child, the result will be the | |||
* result of calling {@code scan} on that child. The child may be a simple node | |||
* result of calling {@code scan} with that child. The child may be a simple node | |||
* or itself a list of nodes. | |||
* <li> If the node being visited has more than one child, the result will |
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.
Inconsistent space after <li>
(Since this is mostly a cleanup PR)
@pavelrappo 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 13 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. ➡️ To integrate this PR with the above commit message to the |
@pavelrappo The following labels will be automatically applied to this pull request:
When this pull request is ready to be reviewed, an "RFR" email will be sent to the corresponding mailing lists. If you would like to change these labels, use the /label pull request command. |
Webrevs
|
/integrate |
@pavelrappo Since your change was applied there have been 16 commits pushed to the
Your commit was automatically rebased without conflicts. Pushed as commit 5a5b807. 💡 You may see a message that your pull request was closed with unmerged commits. This can be safely ignored. |
When a method is said to be called "on an object", this means that the object is a receiver. When a method is said to be called "with an object", this means that the object is a parameter.
To scan an instance of (Doc)Tree, the "scan" method is called on the instance of (Doc)TreeScanner with that instance of (Doc)Tree.
Progress
Issue
Reviewers
Reviewing
Using
git
Checkout this PR locally:
$ git fetch https://git.openjdk.java.net/jdk pull/4174/head:pull/4174
$ git checkout pull/4174
Update a local copy of the PR:
$ git checkout pull/4174
$ git pull https://git.openjdk.java.net/jdk pull/4174/head
Using Skara CLI tools
Checkout this PR locally:
$ git pr checkout 4174
View PR using the GUI difftool:
$ git pr show -t 4174
Using diff file
Download this PR as a diff file:
https://git.openjdk.java.net/jdk/pull/4174.diff