Arrays.asList returned List - Its modifying/write-through semantics (original) (raw)

Jaikiran Pai jai.forums2013 at gmail.com
Fri Aug 17 15:07:41 UTC 2018

Thank you Roger and Stuart for the detailed reply. Comments inline.

On 17/08/18 7:27 AM, Stuart Marks wrote:

Note that while this is changing javadoc and doc comments the task is quite a bit more rigorous than merely updating documentation. The javadoc for public Java SE APIs is a specification and requires very precise language. It's not unusual for what are apparently small changes to go through several rounds of review. (Sorry if you already know this, but I wanted to make sure.) I understand :) I decided to pick this up since it's been around for a few years now and I don't think anyone is in a hurry to have this done. So this will give me enough time to understand the contribution process as well as go through as many review rounds as necessary to get it right.

Whether this requires a CSR depends on whether any normative text of the specification is changed. A simple clarification ("API note") can be added without a CSR. As the wording stands now, however, it seems like there is a mixture of normative and informative statements in the text; these should be teased apart and the informative statements placed into an API note. In addition, the normative text could probably be reworded to be more clear. (See my comments in the bug.) Such changes would probably need a CSR, even though they wouldn't actually change the intent of the specification. If you're still with me, then dive right in! It'll probably be easiest to exchange drafts on the email list. I'll come up with an initial version of the change (based on your inputs that I see in the JIRA) and send it out to this mailing list for review, in the coming days.

Thanks again for the detailed reply.

-Jaikiran

More information about the core-libs-dev mailing list