8288414: Long::compress/expand samples are not correct

[PaulSandoz]

Update the code examples in the api notes of Long::compress/expand. Some constants need to be explicitly long values.

---

Progress

• Change must be properly reviewed (1 review required, with at least 1 Reviewer)
• Change must not contain extraneous whitespace
• Commit message must refer to an issue

Issue

• JDK-8288414: Long::compress/expand samples are not correct

Reviewers

• Alan Bateman (@AlanBateman - Reviewer)

Reviewing

Using git

Checkout this PR locally:
$ git fetch https://git.openjdk.org/jdk19 pull/14/head:pull/14
$ git checkout pull/14

Update a local copy of the PR:
$ git checkout pull/14
$ git pull https://git.openjdk.org/jdk19 pull/14/head

Using Skara CLI tools

Checkout this PR locally:
$ git pr checkout 14

View PR using the GUI difftool:
$ git pr show -t 14

Using diff file

Download this PR as a diff file:
https://git.openjdk.org/jdk19/pull/14.diff

[bridgekeeper]

👋 Welcome back psandoz! A progress list of the required criteria for merging this PR into master will be added to the body of your pull request. There are additional pull request commands available for use with this pull request.

[openjdk]

@PaulSandoz The following label will be automatically applied to this pull request:

• core-libs

When this pull request is ready to be reviewed, an "RFR" email will be sent to the corresponding mailing list. If you would like to change these labels, use the /label pull request command.

[openjdk]

@PaulSandoz 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:

8288414: Long::compress/expand samples are not correct

Reviewed-by: alanb

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 no new commits pushed to the master branch. If another commit should be pushed before you perform the /integrate command, your PR will be automatically rebased. If you prefer to avoid any potential automatic rebasing, please check the documentation for the /integrate command for further details.

➡️ To integrate this PR with the above commit message to the master branch, type /integrate in a new comment.

[mlbridge]

Webrevs

• 00: Full (dc90dd3d)

[PaulSandoz]

/integrate

[openjdk]

Going to push as commit 395aea3.
Since your change was applied there have been 4 commits pushed to the master branch:

• f3b1f60: 8288289: Preview APIs in jdk.jdi, jdk.management, and jdk.jfr should be reflective preview APIs
• 31bc689: 8288324: Loom: Uninitialized JvmtiEnvs in VM_Virtual* ops
• 50f99c3: 8288360: CI: ciInstanceKlass::implementor() is not consistent for well-known classes
• 5a8e1e4: 8287889: (fs) Files.copy description of REPLACE_EXISTING is hard to read

Your commit was automatically rebased without conflicts.

[openjdk]

@PaulSandoz Pushed as commit 395aea3.

💡 You may see a message that your pull request was closed with unmerged commits. This can be safely ignored.