Skip to content

Commit c190674

Browse files
committed
New issue from Jonathan: "Consider changing how get-domain-early(sndr) works"
1 parent 41eb1b6 commit c190674

File tree

1 file changed

+34
-0
lines changed

1 file changed

+34
-0
lines changed

xml/issue4278.xml

Lines changed: 34 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,34 @@
1+
<?xml version='1.0' encoding='utf-8' standalone='no'?>
2+
<!DOCTYPE issue SYSTEM "lwg-issue.dtd">
3+
4+
<issue num="4278" status="New">
5+
<title>Consider changing how <tt><i>get-domain-early</i>(sndr)</tt> works</title>
6+
<section>
7+
<sref ref="[exec.snd.expos]"/>
8+
</section>
9+
<submitter>Jonathan Wakely</submitter>
10+
<date>16 Jun 2025</date>
11+
<priority>99</priority>
12+
13+
<discussion>
14+
<p>
15+
During LWG review of <paper num="P3481R3"/> it was noted that we need to say "except that `sndr`
16+
is only evaluated once" because it's used in <tt><i>get-domain-early</i>(sndr)</tt>, but that
17+
exposition-only-function doesn't actually use its argument, it only cares about the type, and
18+
it default constructs a `Domain` of a type determined by using the type of `sndr`.
19+
<p/>
20+
If we had something like:
21+
</p>
22+
<blockquote><pre>
23+
template&lt;class Sender&gt;
24+
using <i>get-domain-early-t</i> = decltype(<i>get-domain-early</i>(declval&lt;const Sender&amp;&gt;()));
25+
</pre></blockquote>
26+
<p>
27+
then we wouldn't need to use `sndr` twice in expressions that currently use <tt><i>get-domain-early</i>(sndr)</tt>.
28+
</p>
29+
</discussion>
30+
31+
<resolution>
32+
</resolution>
33+
34+
</issue>

0 commit comments

Comments
 (0)