+1
On Thu, Oct 8, 2015 at 6:35 PM, Paul Sandoz <paul.san...@oracle.com> wrote:
>
> > On 8 Oct 2015, at 18:33, mark.reinh...@oracle.com wrote:
> >
> > 2015/10/8 7:56 -0700, d...@cs.oswego.edu:
> >>>> ...
> >>>>
> >>>> class Thread { //
> >>>> /**
> >>>> * A hint to the platform that the current thread is momentarily
> >>>> * unable to progress. ... add more guidance ...
> >>>> */
> >>>> void spinYield();
> >>
> >> should be:
> >> public static void spinYield();
> >
> > Yes -- let's keep this simple. It's just one method, another hint
> > in j.l.Thread which can be ignored (or not) by the VM.
> >
> > This concept seems sufficiently well understood, based on its use
> > in other platforms, that putting it directly into j.l.Thread is not
> > a huge risk. I don't see a strong need for this to start out as a
> > JDK-specific API.
> >
>
> +1
>
> Paul.
>
> _______________________________________________
> Concurrency-interest mailing list
> concurrency-inter...@cs.oswego.edu
> http://cs.oswego.edu/mailman/listinfo/concurrency-interest
>
>
--
Cheers,
√
