-
Notifications
You must be signed in to change notification settings - Fork 1.5k
Stringbuffer cleanup part2 (splitted commits) #1471
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
grigoni
wants to merge
29
commits into
apache:main
Choose a base branch
from
grigoni:feature/cleanup_part2_stringbuffer_splitted
base: main
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Open
Stringbuffer cleanup part2 (splitted commits) #1471
grigoni
wants to merge
29
commits into
apache:main
from
grigoni:feature/cleanup_part2_stringbuffer_splitted
Conversation
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
use StringBuilder in method createCompositeDestination instead of basic String concatenation +=
use StringBuilder instead of StringBuffer in loadJmsMessage method
apply best practices in string collation
avoid StringBuffer and use java 11 String#repeat
avoid StringBuffer and use java 11 String#repeat
rewrite some logging to use params instead of concatenation
use StandardCharsets.UTF_8/US_ASCII which is more robust and does not throw UnsupportedEncodingException
remove StringBuffer where no loop is involved since java compiler will optimize better
rewrite some logging to use params instead of concatenation
use StringBuilder in method createCompositeDestination instead of basic String concatenation +=
use StringBuilder instead of StringBuffer in loadJmsMessage method
apply best practices in string collation
avoid StringBuffer and use java 11 String#repeat
avoid StringBuffer and use java 11 String#repeat
rewrite some logging to use params instead of concatenation
use StandardCharsets.UTF_8/US_ASCII which is more robust and does not throw UnsupportedEncodingException
remove StringBuffer where no loop is involved since java compiler will optimize better
rewrite some logging to use params instead of concatenation
…er_splitted' into feature/cleanup_part2_stringbuffer_splitted
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
about StringBuffer usage, this PR splits changes per type and module
use StringBuilder instead of StringBuffer: this avoids unnecessary sync
use StringBuilder best practice when concatenating
avoid concatenation in logging
use java.nio.charset.StandardCharsets for getBytes
use isEmpty() instead of ...length() > 0
use "0123456789".repeat(Math.max(0, loopSize)); instead of a loop with a SB
some typos fixing
see https://issues.apache.org/jira/browse/AMQ-9732