File tree Expand file tree Collapse file tree 1 file changed +8
-1
lines changed
Expand file tree Collapse file tree 1 file changed +8
-1
lines changed Original file line number Diff line number Diff line change 11<?xml version =' 1.0' encoding =' utf-8' standalone =' no' ?>
22<!DOCTYPE issue SYSTEM "lwg-issue.dtd">
33
4- <issue num =" 4171" status =" New " >
4+ <issue num =" 4171" status =" Tentatively NAD " >
55<title >P2609R3 breaks code that uses `views::zip` and <tt >get< T> </tt ></title >
66<section ><sref ref =" [indirectcallable.indirectinvocable]" /></section >
77<submitter >S. B. Tam</submitter >
@@ -39,6 +39,13 @@ an explicit return type to `fun`.
3939<p />
4040Did LWG foresee this impact of <paper num =" P2609R3" />? Could P2609R3 be reverted to unbreak this code pattern?
4141</p >
42+
43+ <note >2025-10-23; Reflector pool; Status changed: New → Tentatively NAD.</note >
44+ <p >
45+ The range concepts are over-constrained by design, and `indirect_unary_invocable`
46+ was always requiring invokability with `itver_value_t`. The P2609 enforced this
47+ requirement properly for iterators returning proxy references, including `zip_iterator`.
48+ </p >
4249</discussion >
4350
4451<resolution >
You can’t perform that action at this time.
0 commit comments