Talk:Yield method

This redirect is within the scope of WikiProject Computing, a collaborative effort to improve the coverage of computers, computing, and information technology on Wikipedia. If you would like to participate, please visit the project page, where you can join the discussion and see a list of open tasks.ComputingWikipedia:WikiProject ComputingTemplate:WikiProject ComputingComputing articles

Computer science

This redirect is within the scope of WikiProject Computer science, a collaborative effort to improve the coverage of Computer science related articles on Wikipedia. If you would like to participate, please visit the project page, where you can join the discussion and see a list of open tasks.Computer scienceWikipedia:WikiProject Computer scienceTemplate:WikiProject Computer scienceComputer science articles

Things you can help WikiProject Computer science with:

Here are some tasks awaiting attention:

Article requests :
- Requested articles/Applied arts and sciences/Computer science, computing, and Internet
Cleanup :
- Computer science articles needing attention
- Computer science articles needing expert attention
Copyedit :
- Computing
Expand :
- Computer science
Infobox :
- Computer science articles without infoboxes
Maintain :
- Timeline of computing 2020–present
Photo :
- Find pictures for the biographies of computer scientists (see List of computer scientists)
- Computing articles needing images
Stubs :
- Computer science stubs
Unreferenced :
- WikiProject Computer science/Unreferenced BLPs
Project-related :
- Tag all relevant articles in Category:Computer science and sub-categories with {{WikiProject Computer science}}

Yield (multithreading)

I think a more general concept of 'yield (multithreading)' (I'd found this after creating that link in text elsewhere) makes sense. Perhaps it could be worked into the multithreading article e.g. Yield#multithreading, or this article could be rename and generalised. The latter makes sense since a yield *functions* are lower level concepts. the article could then link better to coroutines which also provide yield control

Described Behavior Seems Incorrect

Per Effective Java item 72, "It is within specification for Thread.yield to do nothing at all, simply returning control to its caller. Some modern VMs actually do this ... do not rely on Thread.yield or thread priorities. These facilities are merely hints to the scheduler."

I think the reference to implementing Thread.yield as a no-op is outdated, but the source currently cited in the article also states that behavior is platform dependent - in Java 6 on Windows, "the yielding thread can be scheduled back in one interrupt period later", but on Linux, "a yielded thread will not get another slice of CPU until all other threads have had a slice of CPU" (including threads of lower priority, emphasis in source). 98.69.155.56 (talk) 03:21, 10 July 2011 (UTC)[reply]

Feel free to be bold and fix it. The article could use serious improvement if you are familar with it technically.--v/r - T P 20:32, 10 July 2011 (UTC)[reply]

Topic does not fall in Compiler optimizations category

Topic does not fall in Compiler optimizations category, or at least there is no justification. — Preceding unsigned comment added by 80.102.113.204 (talk) 15:57, 7 April 2013 (UTC)[reply]