Remove field duplication on insertion#41
Open
charlesbr1 wants to merge 4 commits intoquickfix-j:masterfrom
Open
Remove field duplication on insertion#41charlesbr1 wants to merge 4 commits intoquickfix-j:masterfrom
charlesbr1 wants to merge 4 commits intoquickfix-j:masterfrom
Conversation
A cache for frequently used string of integers
All the inserted fields are duplicated : they are converted to StringField, then added to the treeMap. We can remove a lot of allocations by avoiding this behavior. Unless there is a specific reason for this purpose, it seems to works fine without this. Furthermore, the setGroupCount() method allocated the string "1" when there is only one group, this is not efficient.
Fixed a regression (ClassCastException) with components
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
All the inserted fields are duplicated : they are converted to StringField, then added to the treeMap.
We can remove a lot of allocations by avoiding this behavior. Unless there is a specific reason for this purpose, it seems to works fine without this.
The setField(DoubleField field) method got a different implementation from the other because we do not want to allocate a Double instance if the field was built using a double. Hence no null field check are performed for this one.
Furthermore, the setGroupCount() method allocated the string "1" when there is only one group, this is not efficient.