Re: Welcome to the new JSR-375 mailing list
On Mon, May 15, 2017 at 6:19 AM, Will Hopkins <will.hopkins@...> wrote:
It's two ways of thinking about it indeed, one is basically: "the api is the spec, and the pdf only clarifies cross cutting concerns or things that woud be out of place in Javadoc", while the other is what you described.
The JSR process seemingly allows both approaches, which I admit can be confusing.
Nevertheless, the EDR is just a draft of course, and there's no specific requirement that it includes everything that's going to be in the public review.
If needed I can free up some time today and add a section for the feature anyway and/or update the Javadoc to address anything that may be unclear at this point. There went a of lot of thinking, testing and discussion in many things that are now in the API. For feeling would be that if anything was unclear at this point it would largely be a matter of just more carefully writing down any of those decisions being made.