Skip to content

Add user-facing motivations #138

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 1 commit into from
Nov 10, 2025
Merged

Add user-facing motivations #138

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 2 additions & 0 deletions README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -147,6 +147,8 @@ while allowing the developer to write async code largely as they do in cases
without implicit information. The goal is to reduce the mental burden currently
required for special handling async code in such cases.

This proposal aims to lower the barrier for developers to instrument production applications to be able to debug real user problems, enabling the use of tracing tools to collect additional performance metrics and information about code flows. This is a widespread approach used in other programming languages, which has so far not been possible on the web due to the asynchronous nature of many web APIs. Front-end frameworks will use this proposal to reduce and automate boilerplate around attributing async code to specific components, which is currently a source of hard to debug issues.

## Summary

This proposal introduces APIs to propagate a value through asynchronous code,
Expand Down