ByteArrayOutputStream should not have a new writeBytes method in Java 11
martinrb at google.com
Wed Sep 12 00:19:07 UTC 2018
It's an errorprone warning, for "easy" removal ... __IF__ you can run
errorprone on the head sources.
I think it's
On Tue, Sep 11, 2018 at 2:35 PM, Brian Burkhalter
<brian.burkhalter at oracle.com> wrote:
> On Sep 11, 2018, at 1:23 PM, Stuart Marks <stuart.marks at oracle.com> wrote:
>>> 2. even if, it should not be byte b but byte b
>> Yeah we need to clean occurrences of this anachronistic array declaration from the JDK. I noticed a few others nearby. It's startling that a new occurrence has crept it. (Or maybe not, perhaps it was done to conform to the nearby code.)
> Mea culpa. Yes, it was done to conform to existing code in the same class.
More information about the core-libs-dev