优化 StringBuffer 与 StringBuilder 性能说明，避免歧义#2843
Merged
Snailclimb merged 1 commit intoSnailclimb:mainfrom May 3, 2026
Merged
Conversation
原文在性能部分先说明了 StringBuffer 是在原对象上进行修改（不创建新对象）， 随后紧接着对比了 StringBuilder 与 StringBuffer 的性能差异。 这种表述容易让读者产生误解，将“是否创建新对象”与“性能差异”建立关联。 但实际上，StringBuffer 和 StringBuilder 都是在原对象上修改，两者的性能差异主要来源于线程安全机制
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
2 participants
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.
原文在性能部分先说明了 StringBuffer 是在原对象上进行修改（不创建新对象），
随后紧接着对比了 StringBuilder 与 StringBuffer 的性能差异。这种表述可能会让读者将“是否创建新对象”与“性能差异”产生关联
但实际上，StringBuffer 和 StringBuilder 都是在原对象上修改，两者的性能差异主要来源于线程安全机制