added query and customization point documentation

docs/overview.md

@@ -352,8 +352,8 @@ static_assert(not std::execution::unstoppable_token<std::execution::inline_stop_
 </details>
 
 ## Queries
-The queries are used to obtain properties associated with an object. Except <code><a href=‘#forwarding-query’>forwarding_query</a></code>, <code><a href=‘#get-env’>get_env</a></code>, and <code><a href=‘#get-completion-signatures’>get_completion_signatures</a></code> the queries work on <a href=‘#environment’>environments</a>. The
-<a href=‘#environment’>environment</a> queries are defined by providing a member <code>query(<i>query_t</i>, <i>a...</i>) const</code> on the <a href=‘#environment’>environment</a> object.
+The queries are used to obtain properties associated with an object.
+
 <details>
 <summary>Example defining a query on an environment</summary>
 This example shows how to define an environment class which provides a <a href=‘#get-allocator’><code>get_allocator</code></a> query. The objects stores a `std::pmr::memory_resource*` and returns a correspondingly initialized `std::pmr::polymorphic_allocator<>`.
@@ -372,7 +372,14 @@ struct alloc_env {
 <summary><code>forwarding_query(<i>query</i>) -> bool</code></summary>
 **Default**: `false`
 <br/>
-<code>forwarding_query(<i>query</i>)</code> is a `constexpr` query used to determine if the query <code><i>query</i></code> should be forwarded when wrapping an environment.
+The expression <code>forwarding_query(<i>query</i>)</code> is a `constexpr` query used to determine if the query <code><i>query</i></code> should be forwarded when wrapping an environment. The expression is required to be a core constant expression if <code><i>query</i></code> is a core constant expression.
+
+The result of the expression is determined as follows:
+<ol>
+    <li>The result is the value of the expression <code><i>query</i>.query(forwarding_query)</code> if this expression is valid and `noexcept`.</li>
+    <li>The result is <code>true</code> if the type of <code><i>query</i></code> is <code>public</code>ly derived from <code>forwarding_query</code>.</li>
+    <li>Otherwise the result is <code>false</code>.
+</ol>
 <blockquote>
 <details>
 <summary>Example</summary>
@@ -402,7 +409,11 @@ struct custom_t: forwarding_query_t {
 <summary><code>get_env(<i>queryable</i>) -> <i>env</i></code></summary>
 **Default**: <a href='#empty_env'>`empty_env`</a>
 <br/>
-<code>get_env(<i>queryable</i>)</code> is used to get the environment <code><i>env</i></code> associated with <code><i>queryable</i></code>. To provide a non-default environment for a <code><i>queryable</i></code> a `get_env` member needs to be defined. If <code><i>queryable</i></code> doesn’t provide the <code>get_env</code> query an object of type <code><a href=‘#empty_env’>empty_env</a></code> is returned.
+The expresion <code>get_env(<i>queryable</i>)</code> is used to get the environment <code><i>env</i></code> associated with <code><i>queryable</i></code>. To provide a non-default environment for a <code><i>queryable</i></code> a `get_env` member needs to be defined. If <code><i>queryable</i></code> doesn’t provide the <code>get_env</code> query an object of type <code><a href=‘#empty_env’>empty_env</a></code> is returned.
+The value of the expression is <ol>
+   <li>the result of <code>as_const(<i>queryable</i>).get_env()</code> if this expression is valid and <code>noexcept</code>.</li>
+   <li><code>empty_env</code> otherwise.
+</ol>
 <div>
 <details>
 <summary>Example</summary>
@@ -428,7 +439,14 @@ Note that the `get_env` member is both `const` and `noexcept`.
 <summary><code>get_allocator(<i>env</i>) -> <i>allocator</i></code></summary>
 **Default**: <i>none</i>
 <br/>
-<code>get_allocator(<i>env</i>)</code> returns an <code><i>allocator</i></code> for any memory allocations in the respective context. If <code><i>env</i></code> doesn’t support this query any attempt to access it will result in a compilation error.
+The expression <code>get_allocator(<i>env</i>)</code> returns an <code><i>allocator</i></code> for any memory allocations in the respective context. If <code><i>env</i></code> doesn’t support this query any attempt to access it will result in a compilation error.  The value of the expression <code>get_allocator(<i>env</i>)</code> is the result of <code>as_const(<i>env</i>).query(get_allocator)</code> if
+<ul>
+   <li>the expression is valid</code>;</li>
+   <li>the expression is <code>noexcept</code>;</li>
+   <li>the result of the expression satisfies <code><i>simple-allocator</i></code>.</li>
+</ul>
+Otherwise the expression is ill-formed.
+</details>
 <div>
 <details>
 <summary>Example</summary>
@@ -447,47 +465,119 @@ struct alloc_env {
 </div>
 </details>
 <details>
-<summary><code>get_completion_scheduler&lt;<i>tag</i>&gt;(<i>env</i>) -> <i>scheduler</i></code></summary>
+<summary><code>get_completion_scheduler&lt;<iTtag</i>&gt;(<i>env</i>) -> <i>scheduler</i></code></summary>
 **Default**: <i>none</i>
 <br/>
-If the expression <code>get_completion_scheduler&lt;tag&gt;(get_env(<i>sender</i>))</code> is well-formed and returns a scheduler it defines the scheduler on which the completion <code><i>tag</i></code> executes. In particular <code>get_completion_scheduler&lt;set_value_t&gt;(schedule(<i>sched</i>))</code> returns <code><i>sched</i></code>.
+The expression <code>get_complet_scheduler&lt;Tag&gt;(<i>env</i>)</code> yields the completion scheduler for the completion signal <code>Tag</code> associated with <code><i>env</i></code>. This query can be used to determine the scheduler a sender <code><i>sender</i></code> completes on for a given completion signal <code>Tag</code> by using <code>get_completion_scheduler&lt;Tag&gt;(get_env(<i>sender</i>))</code>. The value of the expression is equivalent to <code>as_const(<i>env</i>).query(get_completion_scheduler&lt;Tag&gt;)</code> if
+<ol>
+   <li><code>Tag</code> is one of the types <code>set_value_t</code>, <code>set_error_t</code>, or <code>set_stopped_t</code>;
+   <li>this expression is valid;</li>
+   <li>this expression is <code>noexcept</code>;</li>
+   <li>the expression’s type satisfies <code>scheduler</code>.
+</ol>
+Otherwise the expression is invalid.
 </details>
 <details>
 <summary><code>get_completion_signatures(<i>sender</i>, <i>env</i>)</code></summary>
 The expression <code>get_completion_signatures(<i>sender</i>, <i>env</i>)</code> returns an object whose type is a specialization of <a href=‘#completion-signatures’><code>completion_signatures</code></a> defining the possible completion signatures of <code><i>sender</i></code> when connected to a <a href=‘#receiver’><code><i>receiver</i></code></a> whose <a href=‘#environment'>environment</a> <code>get_env(<i>receiver</i>)</code> is <code><i>env</i></code>. A <a href=‘#sender’><code>sender</code></a> can define the result of this query either by defining a member function <code>get_completion_signatures</code> or using a type alias <code>completion_signatures</code>.
+
+To determine the result the <code><i>sender</i></code> is first transformed using <code>transform_sender(<i>domain</i>, <i>sender</i>, <i>env</i>)</code> to get <code><i>new-sender</i></code> with type <code><i>New-Sender-Type</i></code>. With that the result type is
+<ol>
+    <li>the type of <code><i>new-sender</i>.get_completion_signatures(<i>env</i>)</code> if this expression is valid;</li>
+    <li>the type <code>remove_cvref_t&lt;<i>New-Sender-Type</i>&gt;::completion_signatures</code> if this type exists;</li>
+    <li><code>completion_signatures&lt;set_value_t(<i>T</i>), set_error_t(exception_ptr), set_stopped_t()&gt;</code> if <code><i>New-Sender-Type</i></code> is an awaitable type which would yield an object of type <code><i>T</i></code> when it is <code>co_await</code>ed;</li>
+    <li>invalid otherwise.</code>
+</ol>
 <div>
 <details>
 <summary>Example</summary>
-When a <a href=‘#sender’><code>sender</code></a> doesn’t need to compute the completion signatures based on an <a href=‘#environment’>environment</a> it is easiest to use a the type alias:
-
-
+When a <a href=‘#sender’><code>sender</code></a> doesn’t need to compute the completion signatures based on an <a href=‘#environment’>environment</a> it is easiest to use a the type alias, e.g.:
+```c++
+struct sender {
+    using sender_concept = std::execution::sender_t;
+    using completion_signatures = std::completion_signatures<
+        std::execution::set_value_t(int),
+        std::execution::set_error_t(std::error_code),
+        std::execution::set_stopped()
+    >;
+    // ...
+};
+```
 </details>
 </div>
 </details>
 <details>
-<summary><code>get_delegation_scheduler(<i>env</i>)</code></summary>
+<summary><code>get_delegation_scheduler(<i>env</i>) -> <i>scheduler</i></code></summary>
+The expression <code>get_delegation_scheduler(<i>env</i>)</code> yields the scheduler associated with <code><i>env</i></code> which is used for forward progress delegation. The value of the expression is equivalent to <code>as_const(<i>env</i>).query(get_delegation_scheduler) -> <i>scheduler</i></code> if
+<ol>
+   <li>this expression is valid;</li>
+   <li>this expression is <code>noexcept</code>;</li>
+   <li>the expression’s type satisfies <code>scheduler</code>.
+</ol>
+Otherwise the expression is invalid.
 </details>
 <details>
-<summary><code>get_domain(<i>env</i>)</code>
+<summary><code>get_domain(<i>env</i>) -> <i>domain</i></code>
 </summary>
+The expression <code>get_domain(<i>env</i>)</code> yields the domain associated with <code><i>env</i></code>. The value of the expression is equivalent to <code>as_const(<i>env</i>).query(get_domain)</code> if
+<ol>
+   <li>this expression is valid;</li>
+   <li>this expression is <code>noexcept</code>.</li>
+</ol>
+Otherwise the expression is invalid.
 </details>
 <details>
-<summary><code>get_forward_progress_guarantee(<i>env</i>)</code></summary>
+<summary><code>get_forward_progress_guarantee(<i>scheduler</i>) -> forward_progress_guarantee</code></summary>
+The expression <code>get_forward_progress_guarantee(<i>scheduler</i>)</code> yields the forward progress guarantee of the <i>scheduler</i>’s execution agent. The value of the expression is equivalent to <code>as_const(<i>env</i>).query(get_scheduler)</code> if
+<ol>
+   <li>this expression is valid;</li>
+   <li>this expression is <code>noexcept</code>;</li>
+   <li>the expression’s type is <code>forward_progress_guarantee</code>.
+</ol>
+Otherwise the expression is invalid.
 </details>
 <details>
-<summary><code>get_scheduler(<i>env</i>)</code></summary>
+<summary><code>get_scheduler(<i>env</i>) -> <i>scheduler</i></code></summary>
+The expression <code>get_scheduler(<i>env</i>)</code> yields the scheduler associated with <code><i>env</i></code>. The value of the expression is equivalent to <code>as_const(<i>env</i>).query(get_scheduler)</code> if
+<ol>
+   <li>this expression is valid;</li>
+   <li>this expression is <code>noexcept</code>;</li>
+   <li>the expression’s type satisfies <code>scheduler</code>.
+</ol>
+Otherwise the expression is invalid.
 </details>
 <details>
-<summary><code>get_stop_token(<i>env</i>)</code></summary>
+<summary><code>get_stop_token(<i>env</i>) -> <i>stoppable_token</i></code></summary>
+The expression <code>get_stop_token(<i>env</i>)</code> yields the stop token associated with <code><i>env</i></code>. The value is the result of the expression <code>as_const(<i>env</i>).query(get_stop_token)</code> if
+<ul>
+   <li>the expression is valid;</li>
+   <li>the expression is <code>noexcept</code>;</li>
+   <li>the expression satisfies <code>stoppable_token</code>.</li>
+</ul>
+Otherwise the value is <code>never_stop_token{}</code>.
 </details>
 
-### Customization Point Objects
+## Customization Point Objects
 
-- <code>connect(<i>sender, receiver</i>) -> <i>operation_state</i></code>
-- <code>set_error(<i>error</i>) noexcept -> void</code>
-- <code>set_stopped(<i>receiver</i>) noexcept -> void</code>
-- <code>set_value(<i>receiver, value...</i>) noexcept -> void</code>
-- <code>start(<i>state&amp;</i>) noexcept -> void</code>
+<details>
+<summary><code>connect(<i>sender, receiver</i>) -> <i>operation_state</i></code></summary>
+</details>
+<details>
+<summary><code>set_error(<i>receiver</i>, <i>error</i>) noexcept -> void</code></summary>
+The expression <code>set_error(<i>receiver</i>, <i>error</i>)</code> invokes the <code>set_error</code> completion signal on <code><i>receiver</i></code> with the argument <code><i>error</i></code>, i.e., it invokes <code><i>receiver</i>.set_error(<i>error</i>)</code>.
+</details>
+<details>
+<summary><code>set_stopped(<i>receiver</i>) noexcept -> void</code></summary>
+The expression <code>set_stopped(<i>receiver</i>)</code> invokes the <code>set_stopped</code> completion signal on <code><i>receiver</i></code>, i.e., it invokes <code><i>receiver</i>.set_stopped()</code>.
+</details>
+<details>
+<summary><code>set_value(<i>receiver</i>, <i>value</i>...) noexcept -> void</code></summary>
+The expression <code>set_value(<i>receiver</i>, <i>value</i>...)</code> invokes the <code>set_value</code> completion signal on <code><i>receiver</i></code> with the argument(s) <code><i>value</i>...</code>, i.e., it invokes <code><i>receiver</i>.set_value(<i>value</i>...)</code>.
+</details>
+<details>
+<summary><code>start(<i>state</i>) noexcept -> void</code></summary>
+The expression <code>start(<i>state</i>)</code> starts the execution of the <code>operation_state</code> object <code><i>state</i></code>. Once this expression started executing the object <code><i>state</i></code> is required to stay valid at least until one of the completion signals of <code><i>state</i></code>’s <code>receiver</code> is invoked. Once started exactly one of the completion signals is eventually called.
+</details>
 
 ## Senders