TC39 proposal cancellation
- Dominant language
- JavaScript
- Stars
- 60
- Forks
- 57
- PR merge metrics
- No merged PRs in 30d
Description
There are any plan for [TC39 proposal cancellation](https://github.com/tc39/proposal-cancellation)?
If not:
Based on TC39:
user-controlled cancellation of asynchronous operations through the adoption of a set of native platform objects.
At first, we must have need to asynchronous operations as long as we can use cancelling asynchronous operations that cleared and consistent approach as below:
- Asynchronous functions or iterators
- Fetching remote resources (HTTP, I/O, etc.)
- Interacting with background tasks (Web Workers, forked processes, etc.)
- Long-running operations (animations, etc.)
Contributor guide
Research direction
Start by reading the linked TC39 proposal cancellation document and the http-client entry points built around XMLHttpRequest. Compare the proposal's cancellation goals with the listed asynchronous use cases, then determine whether this repository has a defined cancellation plan. Done means the project's support or non-support decision and its scope are clearly documented.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- api
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100