Why this guidance?

[lant3rn1969]

Hi folks, up above in the Workloads section, you wrote "However, when TAP methods are exposed publicly from a library, they should be provided only for workloads that involve I/O-bound operations.... If a method is purely compute-bound, it should be exposed only as a synchronous implementation." Why this guidance? Typically, I just make everything async and don't trust the consumer of my APIs to know when to offload compute-bound operations. Your documentation, which is largely excellent, would be improved by including your rationale.

---

Document Details

⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

• ID: a50e3d56-6985-0fd2-40b9-155908fec6db
• Version Independent ID: 50355f4c-5763-6977-4b9f-993708037879
• Content: Implementing the Task-based Asynchronous Pattern
• Content Source: docs/standard/asynchronous-programming-patterns/implementing-the-task-based-asynchronous-pattern.md
• Product: dotnet
• GitHub Login: @rpetrusha
• Microsoft Alias: ronpet

[dotnet-bot]

This issue has been closed as part of the issue backlog grooming process outlined in #22351.

That automated process may have closed some issues that should be addressed. If you think this is one of them, reopen it with a comment explaining why. Tag the @dotnet/docs team for visibility.