8000 Update 0000-first-class-support-for-promises.md by btoo · Pull Request #4 · acdlite/rfcs · GitHub
[go: up one dir, main page]
More Web Proxy on the site http://driver.im/
Skip to content

Update 0000-first-class-support-for-promises.md #4

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

Open
wants to merge 1 commit into
base: first-class-promises
Choose a base branch
from
Open

Update 0000-first-class-support-for-promises.md #4

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: 1 addition & 1 deletion text/0000-first-class-support-for-promises.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -421,7 +421,7 @@ const latestValue = use(observable);
Two reasons:

- Promises are not the only ["usable" type](#other-usable-types) — for example, you'll also be able to be `use(Context)`.
- `use` is a very special Hook because [it's allowed be called conditionally](#conditionally-suspending-on-data). The idea is to mitigate confusion by making it the _only_ conditional Hook. Instead of remembering a handful of different conditional Hooks, developers will only have to remember one.
- `use` is a very special Hook because [it's allowed to be called conditionally](#conditionally-suspending-on-data). The idea is to mitigate confusion by making it the _only_ conditional Hook. Instead of remembering a handful of different conditional Hooks, developers will only have to remember one.

## Why can't `use` be called in regular, non-React functions?

Expand Down
0