Skip to content
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

Fixed a render problem in the async discussion page #387

Merged
merged 1 commit into from
Dec 4, 2024
Merged

Fixed a render problem in the async discussion page #387

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
10 changes: 7 additions & 3 deletions doc/qbk/13_async.qbk
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -89,10 +89,14 @@ with this library. Here are some of the most common:
[reflink with_diagnostics] is a completion token adapter that you can use
with async operations when using exceptions. `with_diagnostics` makes
your operations throw [reflink error_with_diagnostics], like sync functions do.
For example:

[async_with_diagnostics_cpp20]
[async_with_diagnostics_cpp11]
`with_diagnostics(asio::deferred)` is the default completion token for most
operations in this library. If you're using C++20 coroutines as suggested in the
tutorials, you're already using it.

When using other completion styles that involve exceptions, like
`asio::yield_context`, you may need to use `with_diagnostics` explicitly.
[link mysql.examples.coroutines_cpp11 This example] shows how to do it.

`with_diagnostics` only makes sense when using exceptions. When using error codes,
you can keep using `asio::as_tuple` and `asio::redirect_error` normally.
Expand Down
Loading