docs: Revise 'Why PTP' section in README#461
Merged
Conversation
Rewrite and clarify the "Why PTP" section: simplified and rephrased bullet points, made Pool/Worker/Work lifecycle and state management explicit, added a link to the sync/async design note, and noted optimizations (CAS, work-stealing, debounce). Also added guidance on suitable scenarios and caveats (when not to use PTP) to help users decide whether the library fits their needs.
Up to standards ✅🟢 Issues
|
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## main #461 +/- ##
=========================================
Coverage 100.00% 100.00%
=========================================
Files 65 65
Lines 5572 5572
Branches 654 654
=========================================
Hits 5572 5572 ☔ View full report in Codecov by Sentry. 🚀 New features to boost your workflow:
|
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Rewrite and clarify the "Why PTP" section: simplified and rephrased bullet points, made Pool/Worker/Work lifecycle and state management explicit, added a link to the sync/async design note, and noted optimizations (CAS, work-stealing, debounce). Also added guidance on suitable scenarios and caveats (when not to use PTP) to help users decide whether the library fits their needs.