Performance of a non-throwing API
Open
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 333
- Forks
- 68
- PR merge metrics
- No merged PRs in 30d
Description
Having an API which returns null or something similar instead of throwing may be useful for performance reasons. We should benchmark and see.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
The issue names no files, tests, APIs, or benchmark entry points. First identify the throwing APIs under consideration and the repository's existing benchmarking setup. Done means a documented benchmark comparison shows whether non-throwing alternatives provide a meaningful performance benefit.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- performance
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100