Topic: Extensions for Disambiguation Tags
Author: Mingxin Wang <wmx16835vv@163.com>
Date: Sun, 8 Oct 2017 19:08:01 -0700 (PDT)
Raw View
------=_Part_5111_544801364.1507514881268
Content-Type: multipart/alternative;
boundary="----=_Part_5112_1429278779.1507514881268"
------=_Part_5112_1429278779.1507514881268
Content-Type: text/plain; charset="UTF-8"
I think the disambiguation tags defined in the standard are not enough to
carry every sort of metadata required by function templates, and therefore
I suggest the following two additional disambiguation tags:
template <class T, T V>
struct in_place_arg_t {
explicit in_place_arg_t() = default;
};
template <class T, T V>
inline constexpr in_place_arg_t<T, V> in_place_arg {};
template <class T, const T& V>
struct in_place_resource_t {
explicit in_place_resource_t() = default;
};
template <class T, const T& V>
inline constexpr in_place_resource_t<T, V> in_place_resource {};
Users are allowed to pass constexpr values by `in_place_arg`, and pass
static constexpr resources by `in_place_resource`.
Additionally, I suggest that `in_place_index_t` should be an alias of
`in_place_arg_t`:
template <size_t I>
using in_place_index_t = in_place_arg_t<size_t, I>;
Moreover, comparing to `in_place_arg_t`, I think `integral_constant` is
inappropriately named, and there seem to be little necessity to define any
member types or constants in it, because these metadata is already passed
by templates. This design is also considered as a solution to another
thread "Constexpr function parameters through special conversions
<https://groups.google.com/a/isocpp.org/forum/#!topic/std-proposals/LANKIrTpaD4>"
started by Nicol Bolas.
The motivation of this design comes from the implementation of another
unpublished proposal of mine about polymorphism (I am still working on it),
and I found it useful when recursively calling constexpr functions in
non-constexpr ones with custom input.
I am looking forward to your comments and suggestions!
Mingxin Wang
--
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/527c448b-b8dd-4877-b63f-b399c167da4d%40isocpp.org.
------=_Part_5112_1429278779.1507514881268
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
<div dir=3D"ltr">I think the disambiguation tags defined in the standard ar=
e not enough to carry every sort of metadata required by function templates=
, and therefore I suggest the following two additional disambiguation tags:=
<br><div><br></div><div><div class=3D"prettyprint" style=3D"background-colo=
r: rgb(250, 250, 250); border-color: rgb(187, 187, 187); border-style: soli=
d; border-width: 1px; word-wrap: break-word;"><code class=3D"prettyprint"><=
div class=3D"subprettyprint"><font color=3D"#660066"><div class=3D"subprett=
yprint">template <class T, T V></div><div class=3D"subprettyprint">st=
ruct in_place_arg_t {</div><div class=3D"subprettyprint">=C2=A0 explicit in=
_place_arg_t() =3D default;</div><div class=3D"subprettyprint">};</div><div=
class=3D"subprettyprint">template <class T, T V></div><div class=3D"=
subprettyprint">inline constexpr in_place_arg_t<T, V> in_place_arg {}=
;</div><div class=3D"subprettyprint"><br></div><div class=3D"subprettyprint=
">template <class T, const T& V></div><div class=3D"subprettyprin=
t">struct in_place_resource_t {</div><div class=3D"subprettyprint">=C2=A0 e=
xplicit in_place_resource_t() =3D default;</div><div class=3D"subprettyprin=
t">};</div><div class=3D"subprettyprint">template <class T, const T&=
V></div><div class=3D"subprettyprint">inline constexpr in_place_resourc=
e_t<T, V> in_place_resource {};</div></font></div></code></div><br><d=
iv>Users are allowed to pass constexpr values by `in_place_arg`, and pass s=
tatic constexpr resources by `in_place_resource`.</div><div><br></div><div>=
Additionally, I suggest that `in_place_index_t` should be an alias of `in_p=
lace_arg_t`:</div></div><div><br></div><div><div class=3D"prettyprint" styl=
e=3D"background-color: rgb(250, 250, 250); border-color: rgb(187, 187, 187)=
; border-style: solid; border-width: 1px; word-wrap: break-word;"><code cla=
ss=3D"prettyprint"><div class=3D"subprettyprint"><div class=3D"subprettypri=
nt">template <size_t I></div><div class=3D"subprettyprint">using in_p=
lace_index_t =3D in_place_arg_t<size_t, I>;</div></div></code></div><=
br><div>Moreover, comparing to `in_place_arg_t`, I think `integral_constant=
` is inappropriately named, and there seem to be little necessity to define=
any member types or constants in it, because these metadata is already pas=
sed by templates. This design is also considered as a solution to another t=
hread "<a href=3D"https://groups.google.com/a/isocpp.org/forum/#!topic=
/std-proposals/LANKIrTpaD4">Constexpr function parameters through special c=
onversions</a>" started by Nicol Bolas.</div><div><br></div><div>The m=
otivation of this design comes from the implementation of another unpublish=
ed proposal of mine about polymorphism (I am still working on it), and I fo=
und it useful when recursively calling constexpr functions in non-constexpr=
ones with custom input.</div><div><br></div><div>I am looking forward to y=
our comments and suggestions!</div><div><br></div><div>Mingxin Wang</div></=
div></div>
<p></p>
-- <br />
You received this message because you are subscribed to the Google Groups &=
quot;ISO C++ Standard - Future Proposals" 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/527c448b-b8dd-4877-b63f-b399c167da4d%=
40isocpp.org?utm_medium=3Demail&utm_source=3Dfooter">https://groups.google.=
com/a/isocpp.org/d/msgid/std-proposals/527c448b-b8dd-4877-b63f-b399c167da4d=
%40isocpp.org</a>.<br />
------=_Part_5112_1429278779.1507514881268--
------=_Part_5111_544801364.1507514881268--
.
Author: Tony V E <tvaneerd@gmail.com>
Date: Mon, 09 Oct 2017 00:02:12 -0400
Raw View
<html><head></head><body lang=3D"en-US" style=3D"background-color: rgb(255,=
255, 255); line-height: initial;"> =
<div style=3D"width: 100%; fo=
nt-size: initial; font-family: Calibri, 'Slate Pro', sans-serif, sans-serif=
; color: rgb(31, 73, 125); text-align: initial; background-color: rgb(255, =
255, 255);">How about some examples showing usage?</div> =
=
<div style=3D"width: 100%; font-size=
: initial; font-family: Calibri, 'Slate Pro', sans-serif, sans-serif; color=
: rgb(31, 73, 125); text-align: initial; background-color: rgb(255, 255, 25=
5);"><br style=3D"display:initial"></div> =
=
=
<div style=3D"font-size: initial; font-family: Calibri, 'Slate P=
ro', sans-serif, sans-serif; color: rgb(31, 73, 125); text-align: initial; =
background-color: rgb(255, 255, 255);">Sent from my BlackBer=
ry portable Babbage Device</div> =
=
=
<table width=3D"100%" style=3D"background-color:white;border-spacing:0px;">=
<tbody><tr><td colspan=3D"2" style=3D"font-size: initial; text-align: init=
ial; background-color: rgb(255, 255, 255);"> <div=
style=3D"border-style: solid none none; border-top-color: rgb(181, 196, 22=
3); border-top-width: 1pt; padding: 3pt 0in 0in; font-family: Tahoma, 'BB A=
lpha Sans', 'Slate Pro'; font-size: 10pt;"> <div><b>From: </b>Mingxin Wang=
</div><div><b>Sent: </b>Sunday, October 8, 2017 10:08 PM</div><div><b>To: <=
/b>ISO C++ Standard - Future Proposals</div><div><b>Reply To: </b>std-propo=
sals@isocpp.org</div><div><b>Subject: </b>[std-proposals] Extensions for Di=
sambiguation Tags</div></div></td></tr></tbody></table><div style=3D"border=
-style: solid none none; border-top-color: rgb(186, 188, 209); border-top-w=
idth: 1pt; font-size: initial; text-align: initial; background-color: rgb(2=
55, 255, 255);"></div><br><div id=3D"_originalContent" style=3D""><div dir=
=3D"ltr">I think the disambiguation tags defined in the standard are not en=
ough to carry every sort of metadata required by function templates, and th=
erefore I suggest the following two additional disambiguation tags:<br><div=
><br></div><div><div class=3D"prettyprint" style=3D"background-color: rgb(2=
50, 250, 250); border-color: rgb(187, 187, 187); border-style: solid; borde=
r-width: 1px; word-wrap: break-word;"><code class=3D"prettyprint"><div clas=
s=3D"subprettyprint"><font color=3D"#660066"><div class=3D"subprettyprint">=
template <class T, T V></div><div class=3D"subprettyprint">struct in_=
place_arg_t {</div><div class=3D"subprettyprint"> explicit in_place_a=
rg_t() =3D default;</div><div class=3D"subprettyprint">};</div><div class=
=3D"subprettyprint">template <class T, T V></div><div class=3D"subpre=
ttyprint">inline constexpr in_place_arg_t<T, V> in_place_arg {};</div=
><div class=3D"subprettyprint"><br></div><div class=3D"subprettyprint">temp=
late <class T, const T& V></div><div class=3D"subprettyprint">str=
uct in_place_resource_t {</div><div class=3D"subprettyprint"> explici=
t in_place_resource_t() =3D default;</div><div class=3D"subprettyprint">};<=
/div><div class=3D"subprettyprint">template <class T, const T& V>=
</div><div class=3D"subprettyprint">inline constexpr in_place_resource_t<=
;T, V> in_place_resource {};</div></font></div></code></div><br><div>Use=
rs are allowed to pass constexpr values by `in_place_arg`, and pass static =
constexpr resources by `in_place_resource`.</div><div><br></div><div>Additi=
onally, I suggest that `in_place_index_t` should be an alias of `in_place_a=
rg_t`:</div></div><div><br></div><div><div class=3D"prettyprint" style=3D"b=
ackground-color: rgb(250, 250, 250); border-color: rgb(187, 187, 187); bord=
er-style: solid; border-width: 1px; word-wrap: break-word;"><code class=3D"=
prettyprint"><div class=3D"subprettyprint"><div class=3D"subprettyprint">te=
mplate <size_t I></div><div class=3D"subprettyprint">using in_place_i=
ndex_t =3D in_place_arg_t<size_t, I>;</div></div></code></div><br><di=
v>Moreover, comparing to `in_place_arg_t`, I think `integral_constant` is i=
nappropriately named, and there seem to be little necessity to define any m=
ember types or constants in it, because these metadata is already passed by=
templates. This design is also considered as a solution to another thread =
"<a href=3D"https://groups.google.com/a/isocpp.org/forum/#!topic/std-propos=
als/LANKIrTpaD4">Constexpr function parameters through special conversions<=
/a>" started by Nicol Bolas.</div><div><br></div><div>The motivation of thi=
s design comes from the implementation of another unpublished proposal of m=
ine about polymorphism (I am still working on it), and I found it useful wh=
en recursively calling constexpr functions in non-constexpr ones with custo=
m input.</div><div><br></div><div>I am looking forward to your comments and=
suggestions!</div><div><br></div><div>Mingxin Wang</div></div></div>
<p></p>
-- <br>
You received this message because you are subscribed to the Google Groups "=
ISO C++ Standard - Future Proposals" 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/527c448b-b8dd-4877-b63f-b399c167da4d%=
40isocpp.org?utm_medium=3Demail&utm_source=3Dfooter">https://groups.goo=
gle.com/a/isocpp.org/d/msgid/std-proposals/527c448b-b8dd-4877-b63f-b399c167=
da4d%40isocpp.org</a>.<br>
<br><!--end of _originalContent --></div></body></html>
<p></p>
-- <br />
You received this message because you are subscribed to the Google Groups &=
quot;ISO C++ Standard - Future Proposals" 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/20171009040212.5161043.12800.37351%40=
gmail.com?utm_medium=3Demail&utm_source=3Dfooter">https://groups.google.com=
/a/isocpp.org/d/msgid/std-proposals/20171009040212.5161043.12800.37351%40gm=
ail.com</a>.<br />
.
Author: Mingxin Wang <wmx16835vv@163.com>
Date: Mon, 9 Oct 2017 08:48:01 -0700 (PDT)
Raw View
------=_Part_2745_1648152961.1507564081963
Content-Type: multipart/alternative;
boundary="----=_Part_2746_1907148332.1507564081963"
------=_Part_2746_1907148332.1507564081963
Content-Type: text/plain; charset="UTF-8"
With the support of `in_place_arg`, it becomes easy to pass any constexpr
value (providing its type is valid for a template non-type parameter) to a
function template using a uniform disambiguation tag, especially with
constructors.
Providing there is a enum class defined as follows:
enum class State {
RUNNINE, AVAILABLE, OFFLINE
};
And there is a constexpr function that could convert a `State` to its
string expression:
constexpr const char* make_state_str(State s) {
switch (s) {
case State::RUNNINE: return "Running State";
case State::AVAILABLE: return "Available State";
case State::OFFLINE: return "Offline State";
default: return "Unknown State";
}
}
It is relatively easy to design a class with `in_place_arg`, which is
explicitly constructible from a `constexpr State` and stores its string
expression without executing the constexpr function `make_state_str` at
runtime:
class Machine {
public:
template <State S>
explicit Machine(std::in_place_arg_t<State, S>) :
state_str_(STATE_STR<S>) {}
const char* get_state_str() { return state_str_; }
private:
const char* state_str_;
template <State S>
static constexpr const char* STATE_STR = make_state_str(S);
};
Machine machine(std::in_place_arg<State, State::AVAILABLE>);
puts(machine.get_state_str());
`in_place_resource` has a wider scope of application than `in_place_arg`
does, because it could carry all sort of constexpr data if the data is
prior declared.
For example, providing there is a struct carries some configuration:
struct Config {
double EPS = 1e-8;
double PI = acos(-1);
int INF = 0x7f7f7f7f;
long long INFL = 0x7f7f7f7f7f7f7f7fL;
} constexpr MATH_CONFIG;
It is allowed to initialize a type with the resource by templates with
`in_place_resource`, even if we are not sure about the concrete type of the
resource:
class Calculator {
public:
template <class T, const T& CONFIG>
explicit Calculator(std::in_place_resource_t<T, CONFIG>);
};
Calculator calculator(std::in_place_resource<Config, MATH_CONFIG>);
Actually, `in_place_resource` could also be used to improve the
implementation in my earlier posts about polymorphism, which used to have
bottleneck on the size (thanks to Nicol Bolas). With the support of
`in_place_resource`, the bottleneck no longer exist, because it becomes
possible to merge the virtual table with the lifetime management functions
at compile time.
Mingxin Wang
On Monday, October 9, 2017 at 12:02:15 PM UTC+8, Tony V E wrote:
>
> How about some examples showing usage?
>
> Sent from my BlackBerry portable Babbage Device
>
--
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/03509464-1e39-4d2f-ba26-c192191e72e6%40isocpp.org.
------=_Part_2746_1907148332.1507564081963
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
<div dir=3D"ltr"><div>With the support of `in_place_arg`, it becomes easy t=
o pass any constexpr value (providing its type is valid for a template non-=
type parameter) to a function template using a uniform disambiguation tag, =
especially with constructors.</div><div><br></div><div>Providing there is a=
enum class defined as follows:</div><div><br></div><div><div class=3D"pret=
typrint" style=3D"background-color: rgb(250, 250, 250); border-color: rgb(1=
87, 187, 187); border-style: solid; border-width: 1px; word-wrap: break-wor=
d;"><code class=3D"prettyprint"><div class=3D"subprettyprint"><div class=3D=
"subprettyprint">enum class State {</div><div class=3D"subprettyprint">=C2=
=A0 RUNNINE, AVAILABLE, OFFLINE</div><div class=3D"subprettyprint">};</div>=
</div></code></div><br>And there is a constexpr function that could convert=
a `State` to its string expression:<br></div><div><br></div><div><div clas=
s=3D"prettyprint" style=3D"background-color: rgb(250, 250, 250); border-col=
or: rgb(187, 187, 187); border-style: solid; border-width: 1px; word-wrap: =
break-word;"><code class=3D"prettyprint"><div class=3D"subprettyprint"><div=
class=3D"subprettyprint">constexpr const char* make_state_str(State s) {</=
div><div class=3D"subprettyprint">=C2=A0 switch (s) {</div><div class=3D"su=
bprettyprint">=C2=A0 =C2=A0 case State::RUNNINE: return "Running State=
";</div><div class=3D"subprettyprint">=C2=A0 =C2=A0 case State::AVAILA=
BLE: return "Available State";</div><div class=3D"subprettyprint"=
>=C2=A0 =C2=A0 case State::OFFLINE: return "Offline State";</div>=
<div class=3D"subprettyprint">=C2=A0 =C2=A0 default: return "Unknown S=
tate";</div><div class=3D"subprettyprint">=C2=A0 }</div><div class=3D"=
subprettyprint">}</div></div></code></div><div><br></div>It is relatively e=
asy to design a class with `in_place_arg`, which is explicitly constructibl=
e from a `constexpr State` and stores its string expression without executi=
ng the constexpr function `make_state_str` at runtime:<br><br></div><div><d=
iv class=3D"prettyprint" style=3D"background-color: rgb(250, 250, 250); bor=
der-color: rgb(187, 187, 187); border-style: solid; border-width: 1px; word=
-wrap: break-word;"><code class=3D"prettyprint"><div class=3D"subprettyprin=
t"><font color=3D"#660066"><div class=3D"subprettyprint">class Machine {</d=
iv><div class=3D"subprettyprint">=C2=A0public:</div><div class=3D"subpretty=
print">=C2=A0 template <State S></div><div class=3D"subprettyprint">=
=C2=A0 explicit Machine(std::in_place_arg_t<State, S>) : state_str_(S=
TATE_STR<S>) {}</div><div class=3D"subprettyprint"><br></div><div cla=
ss=3D"subprettyprint">=C2=A0 const char* get_state_str() { return state_str=
_; }</div><div class=3D"subprettyprint"><br></div><div class=3D"subprettypr=
int">=C2=A0private:</div><div class=3D"subprettyprint">=C2=A0 const char* s=
tate_str_;</div><div class=3D"subprettyprint"><br></div><div class=3D"subpr=
ettyprint">=C2=A0 template <State S></div><div class=3D"subprettyprin=
t">=C2=A0 static constexpr const char* STATE_STR =3D make_state_str(S);</di=
v><div class=3D"subprettyprint">};</div><div class=3D"subprettyprint"><br><=
/div><div class=3D"subprettyprint">Machine machine(std::in_place_arg<Sta=
te, State::AVAILABLE>);</div><div class=3D"subprettyprint">puts(machine.=
get_state_str());</div></font></div></code></div><br><div>`in_place_resourc=
e` has a wider scope of application than `in_place_arg` does, because it co=
uld carry all sort of constexpr data if the data is prior declared.</div><d=
iv><br></div><div>For example, providing there is a struct carries some con=
figuration:</div></div><div><br></div><div><div class=3D"prettyprint" style=
=3D"background-color: rgb(250, 250, 250); border-color: rgb(187, 187, 187);=
border-style: solid; border-width: 1px; word-wrap: break-word;"><code clas=
s=3D"prettyprint"><div class=3D"subprettyprint"><div class=3D"subprettyprin=
t">struct Config {</div><div class=3D"subprettyprint">=C2=A0 double EPS =3D=
1e-8;</div><div class=3D"subprettyprint">=C2=A0 double PI =3D acos(-1);</d=
iv><div class=3D"subprettyprint">=C2=A0 int INF =3D 0x7f7f7f7f;</div><div c=
lass=3D"subprettyprint">=C2=A0 long long INFL =3D 0x7f7f7f7f7f7f7f7fL;</div=
><div class=3D"subprettyprint">} constexpr MATH_CONFIG;</div></div></code><=
/div><br>It is allowed to initialize a type with the resource by templates =
with `in_place_resource`, even if we are not sure about the concrete type o=
f the resource:<br></div><div><br></div><div><div class=3D"prettyprint" sty=
le=3D"background-color: rgb(250, 250, 250); border-color: rgb(187, 187, 187=
); border-style: solid; border-width: 1px; word-wrap: break-word;"><code cl=
ass=3D"prettyprint"><div class=3D"subprettyprint"><font color=3D"#660066"><=
div class=3D"subprettyprint">class Calculator {</div><div class=3D"subprett=
yprint">=C2=A0public:</div><div class=3D"subprettyprint">=C2=A0 template &l=
t;class T, const T& CONFIG></div><div class=3D"subprettyprint">=C2=
=A0 explicit Calculator(std::in_place_resource_t<T, CONFIG>);</div><d=
iv class=3D"subprettyprint">};</div><div class=3D"subprettyprint"><br></div=
><div class=3D"subprettyprint">Calculator calculator(std::in_place_resource=
<Config, MATH_CONFIG>);</div></font></div></code></div><br></div><div=
><div>Actually, `in_place_resource` could also be used to improve the imple=
mentation in my earlier posts about polymorphism, which used to have bottle=
neck on the size (thanks to Nicol Bolas). With the support of `in_place_res=
ource`, the bottleneck no longer exist, because it becomes possible to merg=
e the virtual table with the lifetime management functions at compile time.=
</div><div><br></div><div>Mingxin Wang</div></div><div><br></div><br>On Mon=
day, October 9, 2017 at 12:02:15 PM UTC+8, Tony V E wrote:<blockquote class=
=3D"gmail_quote" style=3D"margin: 0;margin-left: 0.8ex;border-left: 1px #cc=
c solid;padding-left: 1ex;"><div lang=3D"en-US" style=3D"background-color:r=
gb(255,255,255);line-height:initial"> =
<div style=3D"width:100%;fo=
nt-size:initial;font-family:Calibri,'Slate Pro',sans-serif,sans-ser=
if;color:rgb(31,73,125);text-align:initial;background-color:rgb(255,255,255=
)">How about some examples showing usage?</div> =
=
<div style=3D"width:100%;font-size:initial;fo=
nt-family:Calibri,'Slate Pro',sans-serif,sans-serif;color:rgb(31,73=
,125);text-align:initial;background-color:rgb(255,255,255)"><br style=3D"di=
splay:initial"></div> =
=
<div styl=
e=3D"font-size:initial;font-family:Calibri,'Slate Pro',sans-serif,s=
ans-serif;color:rgb(31,73,125);text-align:initial;background-color:rgb(255,=
255,255)">Sent=C2=A0from=C2=A0my=C2=A0BlackBerry=C2=A0<wbr>portable=C2=A0Ba=
bbage=C2=A0Device</div></div>
</blockquote></div>
<p></p>
-- <br />
You received this message because you are subscribed to the Google Groups &=
quot;ISO C++ Standard - Future Proposals" 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/03509464-1e39-4d2f-ba26-c192191e72e6%=
40isocpp.org?utm_medium=3Demail&utm_source=3Dfooter">https://groups.google.=
com/a/isocpp.org/d/msgid/std-proposals/03509464-1e39-4d2f-ba26-c192191e72e6=
%40isocpp.org</a>.<br />
------=_Part_2746_1907148332.1507564081963--
------=_Part_2745_1648152961.1507564081963--
.