--000000000000a28a7b05754c8e58
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

Hi,

   sometimes is important to prevent duplication of enumerators in the
enumerations. That's why some compilers such as clang has the
-Wduplicate-enum.
However there are cases such as ranges within enums, where enumerators
define a category and then are followed by the first element of the
category, with the same value.

enum Ranges
{
    CategoryX =3D 100,
       X1 =3D CategoryX,
       X2,
       X3
     CategoryY =3D 200
       // ...
};

In order to allow such cases coexist with the useful diagnostic, I propose
adding an enumerator attribute, such as [[allow_duplicate]]

enum Ranges
{
    CategoryX =3D 100 [[allow_duplicate]],
       X1 =3D CategoryX,
       X2,
       X3
     CategoryY =3D 200 [[allow_duplicate]]
       // ...
};

This way, we can have the diagnostic and also explicit the intention that
in those cases it is OK to have a repeated value.

Comments?

    Daniel.



--=20
Who=E2=80=99s got the sweetest disposition?
One guess, that=E2=80=99s who?
Who=E2=80=99d never, ever start an argument?
Who never shows a bit of temperament?
Who's never wrong but always right?
Who'd never dream of starting a fight?
Who get stuck with all the bad luck?

--=20
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 e=
mail 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/CAFdMc-39pqfHATmWOA%3DiVNPmGDW0yqGh-jtqrxQPb9ALA=
%3DNK2A%40mail.gmail.com.

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

<div dir=3D"ltr">Hi,<div><br></div><div>=C2=A0 =C2=A0sometimes is important=
 to prevent duplication of enumerators in the enumerations. That&#39;s why =
some compilers such as clang has the -Wduplicate-enum.</div><div>However th=
ere are cases such as ranges within enums, where enumerators define a categ=
ory and then are followed by the first element of the category, with the sa=
me value.</div><div><br></div><div>enum Ranges</div><div>{</div><div>=C2=A0=
 =C2=A0 CategoryX =3D 100,</div><div>=C2=A0 =C2=A0 =C2=A0 =C2=A0X1 =3D Cate=
goryX,</div><div>=C2=A0 =C2=A0 =C2=A0 =C2=A0X2,</div><div>=C2=A0 =C2=A0 =C2=
=A0 =C2=A0X3</div><div>=C2=A0 =C2=A0 =C2=A0CategoryY =3D 200</div><div>=C2=
=A0 =C2=A0 =C2=A0 =C2=A0// ...</div><div>};</div><div><br></div><div>In ord=
er to allow such cases coexist with the useful diagnostic, I propose adding=
 an enumerator attribute, such as [[allow_duplicate]]</div><div><br></div><=
div><div>enum Ranges</div><div>{</div><div>=C2=A0 =C2=A0 CategoryX =3D 100 =
[[allow_duplicate]],</div><div>=C2=A0 =C2=A0 =C2=A0 =C2=A0X1 =3D CategoryX,=
</div><div>=C2=A0 =C2=A0 =C2=A0 =C2=A0X2,</div><div>=C2=A0 =C2=A0 =C2=A0 =
=C2=A0X3</div><div>=C2=A0 =C2=A0 =C2=A0CategoryY =3D 200 [[allow_duplicate]=
]</div><div>=C2=A0 =C2=A0 =C2=A0 =C2=A0// ...</div><div>};</div><div><br></=
div><div>This way, we can have the diagnostic and also explicit the intenti=
on that in those cases it is OK to have a repeated value.</div><div><br></d=
iv><div>Comments?</div><div><br></div><div>=C2=A0 =C2=A0 Daniel.</div><br c=
lass=3D"gmail-Apple-interchange-newline"></div><div><br clear=3D"all"><div>=
<br></div>-- <br><div dir=3D"ltr" class=3D"gmail_signature" data-smartmail=
=3D"gmail_signature">Who=E2=80=99s got the sweetest disposition?<br>One gue=
ss, that=E2=80=99s who?<br>Who=E2=80=99d never, ever start an argument?<br>=
Who never shows a bit of temperament?<br>Who&#39;s never wrong but always r=
ight?<br>Who&#39;d never dream of starting a fight?<br>Who get stuck with a=
ll the bad luck? </div></div></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/CAFdMc-39pqfHATmWOA%3DiVNPmGDW0yqGh-j=
tqrxQPb9ALA%3DNK2A%40mail.gmail.com?utm_medium=3Demail&utm_source=3Dfooter"=
>https://groups.google.com/a/isocpp.org/d/msgid/std-proposals/CAFdMc-39pqfH=
ATmWOA%3DiVNPmGDW0yqGh-jtqrxQPb9ALA%3DNK2A%40mail.gmail.com</a>.<br />

--000000000000a28a7b05754c8e58--

.

------=_Part_444_2067409423.1536351214745
Content-Type: multipart/alternative;
 boundary="----=_Part_445_1561369125.1536351214745"

------=_Part_445_1561369125.1536351214745
Content-Type: text/plain; charset="UTF-8"



On Friday, September 7, 2018 at 2:55:57 PM UTC-4, Daniel Gutson wrote:
>
> Hi,
>
>    sometimes is important to prevent duplication of enumerators in the
> enumerations. That's why some compilers such as clang has the
> -Wduplicate-enum.
> However there are cases such as ranges within enums, where enumerators
> define a category and then are followed by the first element of the
> category, with the same value.
>
> enum Ranges
> {
>     CategoryX = 100,
>        X1 = CategoryX,
>        X2,
>        X3
>      CategoryY = 200
>        // ...
> };
>
> In order to allow such cases coexist with the useful diagnostic, I propose
> adding an enumerator attribute, such as [[allow_duplicate]]
>
> enum Ranges
> {
>     CategoryX = 100 [[allow_duplicate]],
>        X1 = CategoryX,
>        X2,
>        X3
>      CategoryY = 200 [[allow_duplicate]]
>        // ...
> };
>
> This way, we can have the diagnostic and also explicit the intention that
> in those cases it is OK to have a repeated value.
>

That warning triggers only on *implicit* duplicates, so you're all good.

--
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/67f2bf5e-14cf-487f-8d87-9171f49f2ffe%40isocpp.org.

------=_Part_445_1561369125.1536351214745
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><br><br>On Friday, September 7, 2018 at 2:55:57 PM UTC-4, =
Daniel Gutson wrote:<blockquote class=3D"gmail_quote" style=3D"margin: 0;ma=
rgin-left: 0.8ex;border-left: 1px #ccc solid;padding-left: 1ex;"><div dir=
=3D"ltr">Hi,<div><br></div><div>=C2=A0 =C2=A0sometimes is important to prev=
ent duplication of enumerators in the enumerations. That&#39;s why some com=
pilers such as clang has the -Wduplicate-enum.</div><div>However there are =
cases such as ranges within enums, where enumerators define a category and =
then are followed by the first element of the category, with the same value=
..</div><div><br></div><div>enum Ranges</div><div>{</div><div>=C2=A0 =C2=A0 =
CategoryX =3D 100,</div><div>=C2=A0 =C2=A0 =C2=A0 =C2=A0X1 =3D CategoryX,</=
div><div>=C2=A0 =C2=A0 =C2=A0 =C2=A0X2,</div><div>=C2=A0 =C2=A0 =C2=A0 =C2=
=A0X3</div><div>=C2=A0 =C2=A0 =C2=A0CategoryY =3D 200</div><div>=C2=A0 =C2=
=A0 =C2=A0 =C2=A0// ...</div><div>};</div><div><br></div><div>In order to a=
llow such cases coexist with the useful diagnostic, I propose adding an enu=
merator attribute, such as [[allow_duplicate]]</div><div><br></div><div><di=
v>enum Ranges</div><div>{</div><div>=C2=A0 =C2=A0 CategoryX =3D 100 [[allow=
_duplicate]],</div><div>=C2=A0 =C2=A0 =C2=A0 =C2=A0X1 =3D CategoryX,</div><=
div>=C2=A0 =C2=A0 =C2=A0 =C2=A0X2,</div><div>=C2=A0 =C2=A0 =C2=A0 =C2=A0X3<=
/div><div>=C2=A0 =C2=A0 =C2=A0CategoryY =3D 200 [[allow_duplicate]]</div><d=
iv>=C2=A0 =C2=A0 =C2=A0 =C2=A0// ...</div><div>};</div><div><br></div><div>=
This way, we can have the diagnostic and also explicit the intention that i=
n those cases it is OK to have a repeated value.</div></div></div></blockqu=
ote><br><div>That warning triggers only on <i>implicit</i> duplicates, so y=
ou&#39;re all good.<br></div></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/67f2bf5e-14cf-487f-8d87-9171f49f2ffe%=
40isocpp.org?utm_medium=3Demail&utm_source=3Dfooter">https://groups.google.=
com/a/isocpp.org/d/msgid/std-proposals/67f2bf5e-14cf-487f-8d87-9171f49f2ffe=
%40isocpp.org</a>.<br />

------=_Part_445_1561369125.1536351214745--

------=_Part_444_2067409423.1536351214745--

.

------=_Part_474_319017980.1536369092148
Content-Type: multipart/alternative;
 boundary="----=_Part_475_1053782367.1536369092148"

------=_Part_475_1053782367.1536369092148
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

On Friday, September 7, 2018 at 11:55:57 AM UTC-7, Daniel Gutson wrote:
>
> Hi,
>
>    sometimes is important to prevent duplication of enumerators in the=20
> enumerations. That's why some compilers such as clang has the=20
> -Wduplicate-enum.
> However there are cases such as ranges within enums, where enumerators=20
> define a category and then are followed by the first element of the=20
> category, with the same value.
>
> enum Ranges
> {
>     CategoryX =3D 100,
>        X1 =3D CategoryX,
>        X2,
>        X3
>      CategoryY =3D 200
>        // ...
> };
>

What Chris said: this code is already acceptable to Clang.
However, if you do ever run into a situation where Clang is giving you a=20
warning that is "usually correct but I don't want to see it in this=20
particular case," there already exists markup to indicate that situation:

enum Ranges {
    CategoryX =3D 100,
    X1 =3D CategoryX,
    X2,
    X3,
#pragma clang diagnostic push
#pragma clang diagnostic ignored "-Wduplicate-enum"
    DeprecatedNameX1 =3D X1,
    DeprecatedNameX2,
    DeprecatedNameX3,
#pragma clang diagnostic pop
};

Unfortunately, Clang currently has what-I-consider-a-bug in that it=20
requires you to put the pragma on the *first* occurrence of the value,=20
rather than on the *duplicate* occurrence. I've filed a bug report=20
<https://bugs.llvm.org/show_bug.cgi?id=3D38876>.

=E2=80=93Arthur

--=20
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 e=
mail 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/e08984e8-9697-44d9-a603-2af646852647%40isocpp.or=
g.

------=_Part_475_1053782367.1536369092148
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">On Friday, September 7, 2018 at 11:55:57 AM UTC-7, Daniel =
Gutson wrote:<blockquote class=3D"gmail_quote" style=3D"margin: 0;margin-le=
ft: 0.8ex;border-left: 1px #ccc solid;padding-left: 1ex;"><div dir=3D"ltr">=
Hi,<div><br></div><div>=C2=A0 =C2=A0sometimes is important to prevent dupli=
cation of enumerators in the enumerations. That&#39;s why some compilers su=
ch as clang has the -Wduplicate-enum.</div><div>However there are cases suc=
h as ranges within enums, where enumerators define a category and then are =
followed by the first element of the category, with the same value.</div><d=
iv><br></div><div>enum Ranges</div><div>{</div><div>=C2=A0 =C2=A0 CategoryX=
 =3D 100,</div><div>=C2=A0 =C2=A0 =C2=A0 =C2=A0X1 =3D CategoryX,</div><div>=
=C2=A0 =C2=A0 =C2=A0 =C2=A0X2,</div><div>=C2=A0 =C2=A0 =C2=A0 =C2=A0X3</div=
><div>=C2=A0 =C2=A0 =C2=A0CategoryY =3D 200</div><div>=C2=A0 =C2=A0 =C2=A0 =
=C2=A0// ...</div><div>};</div></div></blockquote><div><br></div><div>What =
Chris said: this code is already acceptable to Clang.</div><div>However, if=
 you do ever run into a situation where Clang is giving you a warning that =
is &quot;usually correct but I don&#39;t want to see it in this particular =
case,&quot; there already exists markup to indicate that situation:</div><d=
iv><br></div><div>enum Ranges {</div><div>=C2=A0 =C2=A0 CategoryX =3D 100,<=
/div><div>=C2=A0 =C2=A0 X1 =3D CategoryX,</div><div>=C2=A0 =C2=A0 X2,</div>=
<div>=C2=A0 =C2=A0 X3,</div><div>#pragma clang diagnostic push</div><div>#p=
ragma clang diagnostic ignored &quot;-Wduplicate-enum&quot;</div><div>=C2=
=A0 =C2=A0 DeprecatedNameX1 =3D X1,</div><div>=C2=A0 =C2=A0=C2=A0Deprecated=
NameX2,</div><div>=C2=A0 =C2=A0=C2=A0DeprecatedNameX3,</div><div>#pragma cl=
ang diagnostic pop</div><div>};</div><div><br></div><div>Unfortunately, Cla=
ng currently has what-I-consider-a-bug in that it requires you to put the p=
ragma on the <i>first</i> occurrence of the value, rather than on the <i>du=
plicate</i> occurrence. I&#39;ve filed <a href=3D"https://bugs.llvm.org/sho=
w_bug.cgi?id=3D38876">a bug report</a>.</div><div><br></div><div>=E2=80=93A=
rthur</div></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/e08984e8-9697-44d9-a603-2af646852647%=
40isocpp.org?utm_medium=3Demail&utm_source=3Dfooter">https://groups.google.=
com/a/isocpp.org/d/msgid/std-proposals/e08984e8-9697-44d9-a603-2af646852647=
%40isocpp.org</a>.<br />

------=_Part_475_1053782367.1536369092148--

------=_Part_474_319017980.1536369092148--

.

------=_Part_681_278034914.1536453006087
Content-Type: multipart/alternative;
 boundary="----=_Part_682_1969118459.1536453006088"

------=_Part_682_1969118459.1536453006088
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

I haven't ever had a need for this feature, but since clang supports a=20
warning for it, it seems it might be reasonable to have it as a standard=20
feature. Which is what the OP is asking for?
So it's good you provided the information that there is a solution that=20
might work for his compiler, but would you vote for a standard way to do=20
this? I think that's the question.

On Saturday, September 8, 2018 at 1:11:32 PM UTC+12, Arthur O'Dwyer wrote:

> On Friday, September 7, 2018 at 11:55:57 AM UTC-7, Daniel Gutson wrote:
>>
>> Hi,
>>
>>    sometimes is important to prevent duplication of enumerators in the=
=20
>> enumerations. That's why some compilers such as clang has the=20
>> -Wduplicate-enum.
>> However there are cases such as ranges within enums, where enumerators=
=20
>> define a category and then are followed by the first element of the=20
>> category, with the same value.
>>
>> enum Ranges
>> {
>>     CategoryX =3D 100,
>>        X1 =3D CategoryX,
>>        X2,
>>        X3
>>      CategoryY =3D 200
>>        // ...
>> };
>>
>
> What Chris said: this code is already acceptable to Clang.
> However, if you do ever run into a situation where Clang is giving you a=
=20
> warning that is "usually correct but I don't want to see it in this=20
> particular case," there already exists markup to indicate that situation:
>
> enum Ranges {
>     CategoryX =3D 100,
>     X1 =3D CategoryX,
>     X2,
>     X3,
> #pragma clang diagnostic push
> #pragma clang diagnostic ignored "-Wduplicate-enum"
>     DeprecatedNameX1 =3D X1,
>     DeprecatedNameX2,
>     DeprecatedNameX3,
> #pragma clang diagnostic pop
> };
>
> Unfortunately, Clang currently has what-I-consider-a-bug in that it=20
> requires you to put the pragma on the *first* occurrence of the value,=20
> rather than on the *duplicate* occurrence. I've filed a bug report=20
> <https://bugs.llvm.org/show_bug.cgi?id=3D38876>.
>
> =E2=80=93Arthur
>

--=20
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 e=
mail 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/b6bee554-139b-4673-bbc2-a688a8a35e84%40isocpp.or=
g.

------=_Part_682_1969118459.1536453006088
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div>I haven&#39;t ever had a need for this=C2=A0feature, =
but since clang supports a warning for it, it seems it might be reasonable =
to have it as a standard feature. Which is what the OP is asking for?</div>=
<div>So it&#39;s good you provided the information that there is a solution=
 that might work for his compiler, but would you vote for a standard way to=
 do this? I think=C2=A0that&#39;s the question.<br><br>On Saturday, Septemb=
er 8, 2018 at 1:11:32 PM UTC+12, Arthur O&#39;Dwyer wrote:</div><blockquote=
 class=3D"gmail_quote" style=3D"margin: 0px 0px 0px 0.8ex; padding-left: 1e=
x; border-left-color: rgb(204, 204, 204); border-left-width: 1px; border-le=
ft-style: solid;"><div dir=3D"ltr">On Friday, September 7, 2018 at 11:55:57=
 AM UTC-7, Daniel Gutson wrote:<blockquote class=3D"gmail_quote" style=3D"m=
argin: 0px 0px 0px 0.8ex; padding-left: 1ex; border-left-color: rgb(204, 20=
4, 204); border-left-width: 1px; border-left-style: solid;"><div dir=3D"ltr=
">Hi,<div><br></div><div>=C2=A0 =C2=A0sometimes is important to prevent dup=
lication of enumerators in the enumerations. That&#39;s why some compilers =
such as clang has the -Wduplicate-enum.</div><div>However there are cases s=
uch as ranges within enums, where enumerators define a category and then ar=
e followed by the first element of the category, with the same value.</div>=
<div><br></div><div>enum Ranges</div><div>{</div><div>=C2=A0 =C2=A0 Categor=
yX =3D 100,</div><div>=C2=A0 =C2=A0 =C2=A0 =C2=A0X1 =3D CategoryX,</div><di=
v>=C2=A0 =C2=A0 =C2=A0 =C2=A0X2,</div><div>=C2=A0 =C2=A0 =C2=A0 =C2=A0X3</d=
iv><div>=C2=A0 =C2=A0 =C2=A0CategoryY =3D 200</div><div>=C2=A0 =C2=A0 =C2=
=A0 =C2=A0// ...</div><div>};</div></div></blockquote><div><br></div><div>W=
hat Chris said: this code is already acceptable to Clang.</div><div>However=
, if you do ever run into a situation where Clang is giving you a warning t=
hat is &quot;usually correct but I don&#39;t want to see it in this particu=
lar case,&quot; there already exists markup to indicate that situation:</di=
v><div><br></div><div>enum Ranges {</div><div>=C2=A0 =C2=A0 CategoryX =3D 1=
00,</div><div>=C2=A0 =C2=A0 X1 =3D CategoryX,</div><div>=C2=A0 =C2=A0 X2,</=
div><div>=C2=A0 =C2=A0 X3,</div><div>#pragma clang diagnostic push</div><di=
v>#pragma clang diagnostic ignored &quot;-Wduplicate-enum&quot;</div><div>=
=C2=A0 =C2=A0 DeprecatedNameX1 =3D X1,</div><div>=C2=A0 =C2=A0=C2=A0Depreca=
tedNameX2,</div><div>=C2=A0 =C2=A0=C2=A0DeprecatedNameX3,</div><div>#pragma=
 clang diagnostic pop</div><div>};</div><div><br></div><div>Unfortunately, =
Clang currently has what-I-consider-a-bug in that it requires you to put th=
e pragma on the <i>first</i> occurrence of the value, rather than on the <i=
>duplicate</i> occurrence. I&#39;ve filed <a onmousedown=3D"this.href=3D&#3=
9;https://www.google.com/url?q\x3dhttps%3A%2F%2Fbugs.llvm.org%2Fshow_bug.cg=
i%3Fid%3D38876\x26sa\x3dD\x26sntz\x3d1\x26usg\x3dAFQjCNF8ANaVgaQEaQM-Iu2Rqp=
lUTpeUoQ&#39;;return true;" onclick=3D"this.href=3D&#39;https://www.google.=
com/url?q\x3dhttps%3A%2F%2Fbugs.llvm.org%2Fshow_bug.cgi%3Fid%3D38876\x26sa\=
x3dD\x26sntz\x3d1\x26usg\x3dAFQjCNF8ANaVgaQEaQM-Iu2RqplUTpeUoQ&#39;;return =
true;" href=3D"https://bugs.llvm.org/show_bug.cgi?id=3D38876" target=3D"_bl=
ank" rel=3D"nofollow">a bug report</a>.</div><div><br></div><div>=E2=80=93A=
rthur</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&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/b6bee554-139b-4673-bbc2-a688a8a35e84%=
40isocpp.org?utm_medium=3Demail&utm_source=3Dfooter">https://groups.google.=
com/a/isocpp.org/d/msgid/std-proposals/b6bee554-139b-4673-bbc2-a688a8a35e84=
%40isocpp.org</a>.<br />

------=_Part_682_1969118459.1536453006088--

------=_Part_681_278034914.1536453006087--

.