Skip to content

Use OptionalInt instead of Optional<Integer> #34220

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

Merged
merged 1 commit into from
Oct 2, 2018

Conversation

cbuescher
Copy link
Member

Optionals containing boxed primitive types are prohibitively costly because they
have two level of boxing. For Optional the analogous OptionalInt can be
used to avoid the boxing of the contained int value.

Optionals containing boxed primitive types are prohibitively costly because they
have two level of boxing. For Optional<Integer> the analogous OptionalInt can be
used to avoid the boxing of the contained int value.
@cbuescher cbuescher added >non-issue v7.0.0 :Search Relevance/Ranking Scoring, rescoring, rank evaluation. labels Oct 2, 2018
@elasticmachine
Copy link
Collaborator

Pinging @elastic/es-search-aggs

Copy link
Member

@javanna javanna left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

@cbuescher cbuescher merged commit 5183ea3 into elastic:master Oct 2, 2018
kcm pushed a commit that referenced this pull request Oct 30, 2018
Optionals containing boxed primitive types are prohibitively costly because they
have two level of boxing. For Optional<Integer> the analogous OptionalInt can be
used to avoid the boxing of the contained int value.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants