-
Notifications
You must be signed in to change notification settings - Fork 1.1k
avoiding allocations in FieldCollectorParameters and MergedField #2074
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
bbakerman
merged 2 commits into
graphql-java:master
from
dfa1:field-collector-allocations
Oct 21, 2020
Merged
Changes from all commits
Commits
Show all changes
2 commits
Select commit
Hold shift + click to select a range
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
|
|
@@ -67,7 +67,7 @@ public class MergedField { | |
|
|
||
| private MergedField(List<Field> fields) { | ||
| assertNotEmpty(fields); | ||
| this.fields = unmodifiableList(new ArrayList<>(fields)); | ||
| this.fields = unmodifiableList(fields); | ||
| this.singleField = fields.get(0); | ||
| this.name = singleField.getName(); | ||
| this.resultKey = singleField.getAlias() != null ? singleField.getAlias() : name; | ||
|
|
@@ -144,7 +144,8 @@ public MergedField transform(Consumer<Builder> builderConsumer) { | |
| } | ||
|
|
||
| public static class Builder { | ||
| private List<Field> fields; | ||
|
|
||
| private final List<Field> fields; | ||
|
|
||
| private Builder() { | ||
| this.fields = new ArrayList<>(); | ||
|
|
@@ -155,7 +156,7 @@ private Builder(MergedField existing) { | |
| } | ||
|
|
||
| public Builder fields(List<Field> fields) { | ||
| this.fields = fields; | ||
| this.fields.addAll(fields); | ||
| return this; | ||
|
Contributor
Author
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. used only in tests, could be a breaking change. Maybe this is the root cause of the additional copy that I've just removed in the constructor. |
||
| } | ||
|
|
||
|
|
@@ -168,7 +169,6 @@ public MergedField build() { | |
| return new MergedField(fields); | ||
| } | ||
|
|
||
|
|
||
| } | ||
|
|
||
| @Override | ||
|
|
||
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
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.
This is a tricky one - generally we try for more immutable classes and hence by "copying" we gain some control in mutable Java land
However as this class is repeatedly called, we probably need to change this general pattern if we see evidence that it costs us.
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.
yes, I'm not sure too. I did that because the class is marked as @internal (so we may have more freedom) but I know that it is against the pattern mutable/builder -> immutable/built object.
It looks like it is always called with ExecutionContext data, that is unmodifiable.