RFR : 8185362: Replace use of AtomicReferenceFieldUpdater from BufferedInputStream with Unsafe
martinrb at google.com
Mon Aug 21 15:38:11 UTC 2017
I missed that buf was protected and so the javadoc here actually matters.
Having proper javadoc here for the meaning of null buf (including for
subclasses) "should" be done, but out of scope for this change.
On Mon, Aug 21, 2017 at 8:09 AM, Claes Redestad <claes.redestad at oracle.com>
> Hi Martin,
> On 08/21/2017 04:33 PM, Martin Buchholz wrote:
>> This comment still seems applicable. Can we move it into the docstring
>> for buf?
>> We use nullness
>> - * of buf as primary indicator that this stream is closed. (The
>> - * "in" field is also nulled out on close.)
> this is a reasonable request, the catch is that the field is protected and
> thus visible
> in javadoc, so it needs to be updated as a CSR(?). Perhaps we can move it
> to a regular
> comment associated with the field to avoid this implementation detail
> showing up in
More information about the core-libs-dev