Hi Lance,

> On Jul 18, 2019, at 12:34 PM, Lance Andersen <[email protected]> 
> wrote:
> 
>> One thing which should be considered as an alternative would be not to check 
>> for null at all in these constructors but update the subclass constructor 
>> specifications to override the class documentation and indicate that the 
>> underlying stream parameter may be null.
> 
> I think this might be the better way to go..

Agreed. I therefore withdraw this patch and will use this issue for the back 
out.

Thanks,

Brian

Reply via email to