Thanks to visit codestin.com
Credit goes to github.com

Skip to content

async/await notation for ergonomic asynchronous IO #2394

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 16 commits into from
May 8, 2018
Merged

async/await notation for ergonomic asynchronous IO #2394

Changes from 1 commit
Commits
Show all changes
16 commits
Select commit Hold shift + click to select a range
f63ddca
Async/await.
Apr 5, 2018
8c3d189
Fixed typos
regexident Apr 9, 2018
7b43c7f
Merge pull request #4 from regexident/patch-1
Apr 9, 2018
7cfd755
Typo fix
aturon Apr 20, 2018
411ad1f
Add async blocks
aturon Apr 20, 2018
84c7edf
Rationale for async blocks
aturon Apr 20, 2018
41ce201
Add more rationale for lazy async fn eval
aturon Apr 20, 2018
15b6c9a
Update to match current futures APIs
aturon Apr 20, 2018
822c24c
Grab keywords
aturon Apr 20, 2018
685a588
Reorder async/move
aturon Apr 20, 2018
32b748c
Fix typos
MajorBreakfast Apr 24, 2018
0be451a
Explain use of initialization pattern
MajorBreakfast Apr 24, 2018
f43ad23
`?`-operator and control-flow constructs in async blocks
MajorBreakfast Apr 24, 2018
bcd934a
Ordering of async move keywords
MajorBreakfast Apr 24, 2018
15c2de4
Rename `async for` to `for await`
MajorBreakfast Apr 24, 2018
4059d72
RFC 2394 is async/await syntax.
May 8, 2018
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
Prev Previous commit
Next Next commit
Fix typos
  • Loading branch information
@MajorBreakfast
MajorBreakfast committed Apr 24, 2018
commit 32b748cfa4dbd859dab23740ad95112bbad8084d
8 changes: 4 additions & 4 deletions text/0000-async_await.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -25,7 +25,7 @@ The development of asynchronous IO in Rust has gone through multiple phases.
Prior to 1.0, we experimented with having a green-threading runtime built into
the language. However, this proved too opinionated - because it impacted every
program written in Rust - and it was removed shortly before 1.0. After 1.0,
asynchronous IO initially focused around the mio library, which provided an
asynchronous IO initially focused around the mio library, which provided a
cross-platform abstraction over the async IO primitives of Linux, Mac OS, and
Windows. In mid-2016, the introduction of the futures crate had a major impact
by providing a convenient, shared abstraction for asynchronous operations. The
Expand Down Expand Up @@ -164,7 +164,7 @@ yielding control of the function when it returns `Poll::Pending` and
eventually evaluating to the item value when it returns `Poll::Ready`.

`await!` can only be used inside of an async function, closure, or block.
Using outside of that context is an error.
Using it outside of that context is an error.

(`await!` is a compiler built-in to leave space for deciding its exact syntax
later. See more information in the unresolved questions section.)
Expand Down Expand Up @@ -193,8 +193,8 @@ state, which contains all of the arguments to this function.
The anonymous return type implements `Future`, with the return type as its
`Item`. Polling it advances the state of the function, returning `Pending`
Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Item -> Output

when it hits an `await` point, and `Ready` with the item when it hits a
`return` point. Any attempt to poll it after it has already returned Ready once
will panic.
`return` point. Any attempt to poll it after it has already returned `Ready`
once will panic.

The anonymous return type has a negative impl for the `Unpin` trait - that is
`impl !Unpin`. This is because the future could have internal references which
Expand Down