Skip to content

Re-opened: Generic lowerBound() and upperBound() Utility Methods for Collections and Arrays with 100% Test Coverage #25059

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

Open
wants to merge 2 commits into
base: master
Choose a base branch
from

Conversation

adi1103sh
Copy link

@adi1103sh adi1103sh commented May 6, 2025

This introduces fully tested, generic utility methods:
lowerBound() and upperBound() — for:

Collection

T[] (wrapper/object arrays)

Primitive arrays: int[], long[], char[], short[], float[], double[]

These methods are frequently used in DSA problems, competitive programming, and time-constrained interviews. While C++ developers have access to std::lower_bound and std::upper_bound via STL, Java developers are often forced to re-implement these manually each time — leading to redundancy, reduced productivity, and more boilerplate during contests.

🔥 Key Highlights:

🚀 Optimized binary search logic internally for performance-critical use cases

📦 Supports both object-based and primitive-based containers

📚 Added JavaDocs to all test methods for clarity

💡 Why This Matters:

Reduces friction for Java developers during competitive programming, hackathons, and technical interviews

Brings parity with C++ STL, avoiding time wasted on re-implementing well-known patterns

Enhances reusability in both DSA libraries and production codebases that rely on sorted datasets


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

Error

 ⚠️ OCA signatory status must be verified

Reviewing

Using git

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

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

Using Skara CLI tools

Checkout this PR locally:
$ git pr checkout 25059

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

Using diff file

Download this PR as a diff file:
https://git.openjdk.org/jdk/pull/25059.diff

@bridgekeeper bridgekeeper bot added the oca Needs verification of OCA signatory status label May 6, 2025
@bridgekeeper
Copy link

bridgekeeper bot commented May 6, 2025

Hi @adi1103sh, welcome to this OpenJDK project and thanks for contributing!

We do not recognize you as Contributor and need to ensure you have signed the Oracle Contributor Agreement (OCA). If you have not signed the OCA, please follow the instructions. Please fill in your GitHub username in the "Username" field of the application. Once you have signed the OCA, please let us know by writing /signed in a comment in this pull request.

If you already are an OpenJDK Author, Committer or Reviewer, please click here to open a new issue so that we can record that fact. Please use "Add GitHub user adi1103sh" as summary for the issue.

If you are contributing this work on behalf of your employer and your employer has signed the OCA, please let us know by writing /covered in a comment in this pull request.

@openjdk
Copy link

openjdk bot commented May 6, 2025

❗ This change is not yet ready to be integrated.
See the Progress checklist in the description for automated requirements.

@openjdk
Copy link

openjdk bot commented May 6, 2025

@adi1103sh 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.

@adi1103sh
Copy link
Author

/signed

@bridgekeeper bridgekeeper bot added the oca-verify Needs verification of OCA signatory status label May 6, 2025
@bridgekeeper
Copy link

bridgekeeper bot commented May 6, 2025

Thank you! Please allow for up to two weeks to process your OCA, although it is usually done within one to two business days. Also, please note that pull requests that are pending an OCA check will not usually be evaluated, so your patience is appreciated!

@bridgekeeper
Copy link

bridgekeeper bot commented Jun 3, 2025

@adi1103sh This pull request has been inactive for more than 4 weeks and will be automatically closed if another 4 weeks passes without any activity. To avoid this, simply issue a /touch or /keepalive command to the pull request. Feel free to ask for assistance if you need help with progressing this pull request towards integration!

@adi1103sh
Copy link
Author

/keepalive

@openjdk
Copy link

openjdk bot commented Jun 4, 2025

@adi1103sh The pull request is being re-evaluated and the inactivity timeout has been reset.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
core-libs [email protected] oca Needs verification of OCA signatory status oca-verify Needs verification of OCA signatory status
Development

Successfully merging this pull request may close these issues.

1 participant