Replaced StringBuffer with StringBuilder in WcCommand.java:251

[opencode-agent]

Done. Replaced StringBuffer with StringBuilder in the print method at line 251 of WcCommand.java. This is a local, single-threaded context so StringBuilder avoids unnecessary synchronization overhead.

Closes #532

opencode session  |  github run

[LSantha]

/oc review

[opencode-agent]

The change is correct. StringBuilder is the appropriate choice here since:

1. The print method is called from printLine → printResults → execute - all single-threaded
2. No shared buffer or thread-safety concerns exist
3. StringBuilder avoids unnecessary synchronization overhead

No other StringBuffer usages exist in this file. The change is minimal, localized, and improves performance. LGTM.

opencode session  |  github run

[LSantha]

/oc review

[opencode-agent]

The change is correct. Line 251 now uses StringBuilder instead of StringBuffer:

StringBuilder sValue = new StringBuilder(paddingSize + 1);

Analysis:

• The print method (line 250-261) is called from printLine → printResults → execute - all single-threaded command execution
• No shared buffer or thread-safety concerns exist
• StringBuilder avoids unnecessary synchronization overhead

The change is minimal, localized, and improves performance. LGTM.

opencode session  |  github run

[LSantha]

/oc review

[opencode-agent]

The change is correct. Line 251 now uses StringBuilder instead of StringBuffer:

StringBuilder sValue = new StringBuilder(paddingSize + 1);

Analysis:

• The print method (lines 250-261) is called from printLine → printResults → execute - all single-threaded command execution
• No shared buffer or thread-safety concerns exist
• StringBuilder avoids unnecessary synchronization overhead

The change is minimal, localized, and improves performance. LGTM.

opencode session  |  github run

[LSantha]

Superseded by #541, which already merged the same WcCommand StringBuilder change into master.