Skip to content

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
wants to merge 29 commits into
base: main
Choose a base branch
from

Conversation

grigoni
Copy link
Contributor

@grigoni grigoni commented Jul 8, 2025

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

giana added 14 commits July 8, 2025 05:52
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
@grigoni grigoni changed the title Feature/cleanup part2 stringbuffer splitted Stringbuffer cleanup part2 (splitted commits) Jul 8, 2025
giana added 14 commits July 9, 2025 23:00
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
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant