Rename ThreadPool 'Overflow' terminology to 'Saturated' for clarity #122910
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
Renamed thread pool state terminology from "Overflow" to "Saturated" to better describe the condition where the pool has reached maximum capacity with pending work requests.
The term "overflow" incorrectly suggested an integer wraparound bug rather than the intended meaning: the pool is at capacity but has unserviced work requests. "Saturated" is semantically accurate and industry-standard for resources at maximum capacity.
Changes
IsOverflowproperty →IsSaturatedPortableThreadPool.ThreadCounts.csPortableThreadPool.WorkerThread.csComments referring to actual integer overflow (wraparound) were intentionally preserved.
Customer Impact
No customer impact - internal terminology change only. No API or behavioral changes.
Regression
No. Terminology-only change addressing feedback in PR #122726.
Testing
Code is syntactically verified. No logic changes.
Risk
Minimal. Property and comment renaming only, no behavioral changes.
Original prompt
✨ Let Copilot coding agent set things up for you — coding agent works faster and does higher quality work when set up for your repo.