Re: [jdk22] RFR: 8322512: StringBuffer.repeat does not work correctly after toString() was called [v2]

On Wed, 17 Jan 2024 15:01:07 GMT, Jim Laskey wrote: >> The new repeat methods were not clearing the toStringCache. > > Jim Laskey has updated the pull request with a new target base due to a merge > or a rebase. The incremental webrev excludes the unrelated changes brought in > by the

Re: [jdk22] RFR: 8322512: StringBuffer.repeat does not work correctly after toString() was called [v2]

> The new repeat methods were not clearing the toStringCache. Jim Laskey has updated the pull request with a new target base due to a merge or a rebase. The incremental webrev excludes the unrelated changes brought in by the merge/rebase. The pull request contains two additional commits since

Re: [jdk22] RFR: 8322512: StringBuffer.repeat does not work correctly after toString() was called

On Wed, 17 Jan 2024 14:21:22 GMT, Jim Laskey wrote: > The new repeat methods were not clearing the toStringCache. Jim, note that the bot said this: > At the time when this comment was updated there had been 64 new commits > pushed to the master branch: I'm not sure why there's such a big

Re: [jdk22] RFR: 8322512: StringBuffer.repeat does not work correctly after toString() was called

On Wed, 17 Jan 2024 14:21:22 GMT, Jim Laskey wrote: > The new repeat methods were not clearing the toStringCache. Seems like a clean backport of a P3 bug from mainline to jdk 22, just in time before RDP 2. - Marked as reviewed by prappo (Reviewer). PR Review:

[jdk22] RFR: 8322512: StringBuffer.repeat does not work correctly after toString() was called

The new repeat methods were not clearing the toStringCache. - Commit messages: - Backport df22fb322e6c4c9931a770bd0abf4c43b83c4e4a Changes: https://git.openjdk.org/jdk22/pull/87/files Webrev: https://webrevs.openjdk.org/?repo=jdk22=87=00 Issue: