JEP 110: leeway for API changes?

[Michael McMahon]

Hi,

API changes are still possible. Sorry, I haven't gotten around
to replying to all feedback, but I will do this week.

Thanks
Michael

On 19/05/16 15:02, Simone Bordet wrote:
> Hi,
>
> On Thu, May 19, 2016 at 3:54 PM, Anthony Vanelverdinghe
> <anthony.vanelverdinghe at gmail.com> wrote:
>> Hi
>>
>> With the JDK's "Feature Complete" milestone coming up next week: how much
>> leeway is there still for API changes? I've made API suggestions (a.o. in
>> [1]), ranging from changing HttpResponse.multiProcessor::onStart's return
>> type (from BiFunction<..., Boolean> to BiPredicate), to building on the
>> j.u.c.Flow API & eliminating HttpResponse.MultiProcessor. So I'm wondering
>> what's still on on the table for JEP 110 w.r.t. API changes?
> I second that. I also made API change proposals, but no feedback.
>