Lets review the answer given by the or-acle; [Thread.yield()](https://docs.oracle.com/en/java/javase/11/docs/api/java.base/java/lang/Thread.html#yield())
Firstly its an method which requires no input and has no output.
Secondly its an hint without predefined usage pattern or functional outcome.
The other paragraphs try to explain its usage, but fail to add an example like;
Running multi-processor code on single cpu OR on an over-utilise cpus requires yielding to avoid async deadlocks in parallel work distributions trees.
Also in high performance parallel code, yielding control out of consent, may result in better performance than forced interruption or time slicing.
Especially when working with an live non-homogeneous workload.
Writing and simulating parallel code paths is not easy. So most developers use a library which comes with default configured options.
Then feed it small batches of work and hope for the best.
Now simulate with ~7833661741 threads using X different libraries and try to avoid deadlocks.
By replacing a few words, this changes the description to the faith-by-math yielding version;
A hint to the π-creator that the current human is willing to yield its current use of a itself.
