Ship R2 (2021-10-15 mailing).

Author: brycelelbach

P2300R2.html

@@ -1560,10 +1560,9 @@
     blockquote c-[vi] { color: inherit; } /* Name.Variable.Instance */
     blockquote c-[il] { color: inherit; } /* Literal.Number.Integer.Long */
   </style>
-  <meta content="Bikeshed version 4f053d00e, updated Tue Aug 10 14:13:32 2021 -0700" name="generator">
+  <meta content="Bikeshed version a210b7d86, updated Thu Sep 16 13:45:19 2021 -0700" name="generator">
   <link href="https://wg21.link/P2300" rel="canonical">
   <link href="https://isocpp.org/favicon.ico" rel="icon">
-  <meta content="06b903afb686b73f0a60a1c53af1880853c9d09d" name="document-revision">
 <style>
 pre {
   margin-top: 0px;
@@ -1876,6 +1875,16 @@
 
 .dfn-paneled { cursor: pointer; }
 </style>
+<style>/* style-issues */
+
+a[href].issue-return {
+    float: right;
+    float: inline-end;
+    color: var(--issueheading-text);
+    font-weight: bold;
+    text-decoration: none;
+}
+</style>
 <style>/* style-md-lists */
 
 /* This is a weird hack for me not yet following the commonmark spec
@@ -2185,7 +2194,7 @@
   <div class="head">
    <p data-fill-with="logo"></p>
    <h1 class="p-name no-ref" id="title">P2300R2<br><code class="highlight"><c- n>std</c-><c- o>::</c-><c- n>execution</c-></code></h1>
-   <h2 class="no-num no-toc no-ref heading settled" id="profile-and-date"><span class="content">Draft Proposal, <time class="dt-updated" datetime="2021-10-01">2021-10-01</time></span></h2>
+   <h2 class="no-num no-toc no-ref heading settled" id="profile-and-date"><span class="content">Published Proposal, <time class="dt-updated" datetime="2021-10-04">2021-10-04</time></span></h2>
    <div data-fill-with="spec-metadata">
     <dl>
      <dt class="editor">Authors:
@@ -2241,7 +2250,7 @@ <h2 class="no-num no-toc no-ref" id="contents">Table of Contents</h2>
        <a href="#example-schedulers"><span class="secno">1.5</span> <span class="content">Examples: Schedulers</span></a>
        <ol class="toc">
         <li><a href="#example-schedulers-inline"><span class="secno">1.5.1</span> <span class="content">Inline scheduler</span></a>
-        <li><a href="#example-single-thread"><span class="secno">1.5.2</span> <span class="content">Single Thread Scheduler</span></a>
+        <li><a href="#example-single-thread"><span class="secno">1.5.2</span> <span class="content">Single thread scheduler</span></a>
        </ol>
       <li><a href="#intro-is-not"><span class="secno">1.6</span> <span class="content">What this proposal is <strong>not</strong></span></a>
       <li><a href="#intro-compare"><span class="secno">1.7</span> <span class="content">Design changes from P0443</span></a>
@@ -2942,7 +2951,7 @@ <h4 class="heading settled" data-level="1.5.1" id="example-schedulers-inline"><s
     <li data-md>
      <p>The operation state customizes <code class="highlight"><c- n>std</c-><c- o>::</c-><c- n>execution</c-><c- o>::</c-><c- n>start</c-></code> to call <code class="highlight"><c- n>std</c-><c- o>::</c-><c- n>execution</c-><c- o>::</c-><c- n>set_value</c-></code> on the receiver, passing any exceptions to <code class="highlight"><c- n>std</c-><c- o>::</c-><c- n>execution</c-><c- o>::</c-><c- n>set_error</c-></code> as an <code class="highlight"><c- n>exception_ptr</c-></code>.</p>
    </ol>
-   <h4 class="heading settled" data-level="1.5.2" id="example-single-thread"><span class="secno">1.5.2. </span><span class="content">Single Thread Scheduler</span><a class="self-link" href="#example-single-thread"></a></h4>
+   <h4 class="heading settled" data-level="1.5.2" id="example-single-thread"><span class="secno">1.5.2. </span><span class="content">Single thread scheduler</span><a class="self-link" href="#example-single-thread"></a></h4>
    <p>This example shows how to create a scheduler for an execution context that consists of a single
 thread. It is implemented in terms of a lower-level execution context called <code class="highlight"><c- n>manual_event_loop</c-></code>.</p>
 <pre class="language-c++ highlight"><c- n>class</c-> <c- n>single_thread_context</c-> <c- p>{</c->

std_execution.bs

@@ -1,9 +1,9 @@
 <pre class='metadata'>
 Title: `std::execution`
 H1: <code>std::execution</code>
-Shortname: D2300
+Shortname: P2300
 Revision: 2
-Status: D
+Status: P
 Group: WG21
 Audience: SG1, LEWG
 Editor: Michał Dominiak, [email protected]
@@ -295,7 +295,7 @@ You can find the example [here](https://github.com/kirkshoop/libunifex/blob/file
 
 Dietmar Kuehl has a hobby project that implements networking APIs on top of sender/receiver. He recently implemented an echo server as a demo. His echo server code can be found [here](https://github.com/dietmarkuehl/kuhllib/blob/main/src/examples/echo_server.cpp).
 
-Below, I show the part of the echo server code. This code is executed for each client that connects to the echo server. In a loop, it reads input from a socket and echos the input back to the same socket. All of this, including the loop, is implemented with generic async algorithms. 
+Below, I show the part of the echo server code. This code is executed for each client that connects to the echo server. In a loop, it reads input from a socket and echos the input back to the same socket. All of this, including the loop, is implemented with generic async algorithms.
 
     <pre highlight="c++">
     outstanding.start(
@@ -556,7 +556,7 @@ implementing one. The `inline_scheduler`:
     on the receiver, passing any exceptions to `std::execution::set_error` as an
     `exception_ptr`.
 
-### Single Thread Scheduler ### {#example-single-thread}
+### Single thread scheduler ### {#example-single-thread}
 
 This example shows how to create a scheduler for an execution context that consists of a single
 thread. It is implemented in terms of a lower-level execution context called `manual_event_loop`.