--94eb2c1a213af7bc5d0554820c88
Content-Type: text/plain; charset="UTF-8"

INVOKE<R>: http://eel.is/c++draft/func.require#2

Do consider mentioning the cvref-qualifiers on the signature, as was
proposed for std::function (like `function_ref<void () const>`). Maybe just
as a "future extensions" thing, but it'd be good to have "the author of
this proposal sees the value of ..." in writing.

In fact I'd prefer it to only accept things that are callable as non-const
when no cvref-qualifiers are provided, but that'd break symmetry with
std::function and I'm not sure how eager LEWG would be for that.

On Mon, Jul 17, 2017 at 1:33 PM Vittorio Romeo <vittorio.romeo.vee@gmail.com>
wrote:

> Thanks everyone for the feedback.
>
> So far I have:
> * Fixed the typos (double colon, "requires" instead of "remarks") found by
> T.C..
> * Marked `swap` as `noexcept` and defined the non-member `swap` in terms
> of the member one.
>
> Regarding the "empty state": I will think about this and add a small
> section in the paper discussing pros&cons.
> I couldn't find anything regarding `INVOKE<R>`. Where can I find more
> information about that?
>
> I will also look into a `noexcept` specialization.
>
> --
> You received this message because you are subscribed to the Google Groups
> "ISO C++ Standard - Future Proposals" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to std-proposals+unsubscribe@isocpp.org.
> To post to this group, send email to std-proposals@isocpp.org.
> To view this discussion on the web visit
> https://groups.google.com/a/isocpp.org/d/msgid/std-proposals/e952b0e4-f989-4ee1-a554-e306c9278191%40isocpp.org
> <https://groups.google.com/a/isocpp.org/d/msgid/std-proposals/e952b0e4-f989-4ee1-a554-e306c9278191%40isocpp.org?utm_medium=email&utm_source=footer>
> .
>

--
You received this message because you are subscribed to the Google Groups "ISO C++ Standard - Future Proposals" group.
To unsubscribe from this group and stop receiving emails from it, send an email to std-proposals+unsubscribe@isocpp.org.
To post to this group, send email to std-proposals@isocpp.org.
To view this discussion on the web visit https://groups.google.com/a/isocpp.org/d/msgid/std-proposals/CAPCFJdQ1c2Er2RQ5AgiurUHAri8qyX_bvJbjyHYU4RYkSCgJ%3DQ%40mail.gmail.com.

--94eb2c1a213af7bc5d0554820c88
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">INVOKE&lt;R&gt;:=C2=A0<a href=3D"http://eel.is/c++draft/fu=
nc.require#2">http://eel.is/c++draft/func.require#2</a><div><br></div><div>=
Do consider mentioning the cvref-qualifiers on the signature, as was propos=
ed for std::function (like `function_ref&lt;void () const&gt;`). Maybe just=
 as a &quot;future extensions&quot; thing, but it&#39;d be good to have &qu=
ot;the author of this proposal sees the value of ...&quot; in writing.</div=
><div><br></div><div>In fact I&#39;d prefer it to only accept things that a=
re callable as non-const when no cvref-qualifiers are provided, but that&#3=
9;d break symmetry with std::function and I&#39;m not sure how eager LEWG w=
ould be for that.</div></div><br><div class=3D"gmail_quote"><div dir=3D"ltr=
">On Mon, Jul 17, 2017 at 1:33 PM Vittorio Romeo &lt;<a href=3D"mailto:vitt=
orio.romeo.vee@gmail.com">vittorio.romeo.vee@gmail.com</a>&gt; wrote:<br></=
div><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-lef=
t:1px #ccc solid;padding-left:1ex"><div dir=3D"ltr">Thanks everyone for the=
 feedback.=C2=A0<br><br>So far I have:<br>* Fixed the typos (double colon, =
&quot;requires&quot; instead of &quot;remarks&quot;) found by T.C..<br>* Ma=
rked `swap` as `noexcept` and defined the non-member `swap` in terms of the=
 member one.<br><br>Regarding the &quot;empty state&quot;: I will think abo=
ut this and add a small section in the paper discussing pros&amp;cons.<br>I=
 couldn&#39;t find anything regarding `INVOKE&lt;R&gt;`. Where can I find m=
ore information about that?<br><br>I will also look into a `noexcept` speci=
alization.</div>

<p></p>

-- <br>
You received this message because you are subscribed to the Google Groups &=
quot;ISO C++ Standard - Future Proposals&quot; group.<br>
To unsubscribe from this group and stop receiving emails from it, send an e=
mail to <a href=3D"mailto:std-proposals+unsubscribe@isocpp.org" target=3D"_=
blank">std-proposals+unsubscribe@isocpp.org</a>.<br>
To post to this group, send email to <a href=3D"mailto:std-proposals@isocpp=
..org" target=3D"_blank">std-proposals@isocpp.org</a>.<br>
To view this discussion on the web visit <a href=3D"https://groups.google.c=
om/a/isocpp.org/d/msgid/std-proposals/e952b0e4-f989-4ee1-a554-e306c9278191%=
40isocpp.org?utm_medium=3Demail&amp;utm_source=3Dfooter" target=3D"_blank">=
https://groups.google.com/a/isocpp.org/d/msgid/std-proposals/e952b0e4-f989-=
4ee1-a554-e306c9278191%40isocpp.org</a>.<br>
</blockquote></div>

<p></p>

-- <br />
You received this message because you are subscribed to the Google Groups &=
quot;ISO C++ Standard - Future Proposals&quot; group.<br />
To unsubscribe from this group and stop receiving emails from it, send an e=
mail to <a href=3D"mailto:std-proposals+unsubscribe@isocpp.org">std-proposa=
ls+unsubscribe@isocpp.org</a>.<br />
To post to this group, send email to <a href=3D"mailto:std-proposals@isocpp=
..org">std-proposals@isocpp.org</a>.<br />
To view this discussion on the web visit <a href=3D"https://groups.google.c=
om/a/isocpp.org/d/msgid/std-proposals/CAPCFJdQ1c2Er2RQ5AgiurUHAri8qyX_bvJbj=
yHYU4RYkSCgJ%3DQ%40mail.gmail.com?utm_medium=3Demail&utm_source=3Dfooter">h=
ttps://groups.google.com/a/isocpp.org/d/msgid/std-proposals/CAPCFJdQ1c2Er2R=
Q5AgiurUHAri8qyX_bvJbjyHYU4RYkSCgJ%3DQ%40mail.gmail.com</a>.<br />

--94eb2c1a213af7bc5d0554820c88--

.