Totally appreciate the suggestion that the java.util.concurrent modifications be done by folks with more domain expertise.
Would you have us incorporate the initial minimal set of j.u.c. updates or none at all? thanks, Karen > On Nov 11, 2015, at 8:09 PM, Doug Lea <d...@cs.oswego.edu> wrote: > > On 11/10/2015 12:38 PM, frederic parain wrote: > >>> If I put on some extra-strength rose-coloured glasses I think I can >>> almost read that as "something is better than nothing". ;-) > > Yeah, that's what I meant :-) It is good to at least have the > @ReservedStackAccess annotation and mechanism in place. Finding > the best way to use it will take more thought and empirical evaluation. > > So I suggest that the hotspot support part of the webrev be put into place, > and that we incorporate j.u.c updates using it after further exploration > and evaluation -- we do have a lot of tests using locks etc, so are in > a better position to make better decisions about alternative placement > strategies after trying them. > >>> But note that it is not the finally part that need be at issue. > > Right. But given the existence of @ReservedStackAccess, we might be > able to rework some code so as to use it more sparingly. > > -Doug > >
