Hi Jaikiran,
Improving the documentation of the current behavior would be a good
contribution
and first step. It will need a CSR since it needs to be checked that it
accurately
describes the behavior but that will be pretty straightforward once the
change is reviewed.
Note that Collection.remove("b") is following its specified behavior
that is based on iterating
over the contents of the Collection. Only if the value is not found,
will it attempt to remove
and get the exception.
Regards, Roger
On 8/16/18 4:38 AM, Jaikiran Pai wrote:
Hi Ivan,
On 15/08/18 4:27 PM, Jaikiran Pai wrote:
Hi Ivan,
On 15/08/18 1:20 PM, Ivan Gerasimov wrote:
Hi Jaikiran!
The first part (the documentation clarification) was requested some
time ago [1], so it may be eventually fixed.
[1] https://bugs.openjdk.java.net/browse/JDK-7033681
Thank you for pointing to that one. I hadn't found it during my search
before sending this mail.
Is this JIRA/change, something that I can contribute? If so, what would
be the typical process for that? I have signed and approved OCA, but I
don't know what's involved in submitting changes which involve javadoc
changes - does this need CSR and will that CSR have to be filed after I
submit the initial draft of the changed javadoc?
-Jaikiran
