You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: std_execution.bs
+2-2
Original file line number
Diff line number
Diff line change
@@ -1015,7 +1015,7 @@ relieve the user from having to deal with low-level details of cancellation.
1015
1015
### Cancellation design summary ###
1016
1016
1017
1017
The design of cancellation described in this paper is built on top of and extends the `std::stop_token`-based
1018
-
cancellation facilities added in C++20, first proposed in [P2175R0](https://wg21.link/P2175R0).
1018
+
cancellation facilities added in C++20, first proposed in [[P2175R0]].
1019
1019
1020
1020
At a high-level, the facilities proposed by this paper for supporting cancellation include:
1021
1021
* Add `std::stoppable_token` and `std::stoppable_token_for` concepts that generalise the interface of `std::stop_token` type to allow other types with different implementation strategies.
@@ -1086,7 +1086,7 @@ For an example of an implementation strategy for solving these data-races see th
1086
1086
### Cancellation design status ###
1087
1087
1088
1088
This paper currently includes the design for cancellation as proposed in
1089
-
[P2175R0](https://wg21.link/P2175R0) - "Composable cancellation for sender-based async operations".
1089
+
[[P2175R0]] - "Composable cancellation for sender-based async operations".
1090
1090
P2175R0 contains more details on the background motivation and prior-art and design rationale of this design.
1091
1091
1092
1092
It is important to note, however, that initial review of this design in the SG1 concurrency subgroup raised some concerns
0 commit comments