Hello,

Me and a few other people in Russia wish to add extended integer types
to the C++ Standard (like int128, int256...).

It looks possible to implement that idea as a library only solution.
The interface will be close to this:

// Class for extended integer types
template <size_t Bits, bool IsSigned = true>
class integer {
    static_assert(is_power_of_2(Bits), "");
    // ...
    // all the arithmetic and comparison operators
    // ...
};

using int128_t = integer<128>;
using int256_t = integer<256>;
using int512_t = integer<512>;

constexpr integer<128> operator "" _int128(const char*);
constexpr integer<256> operator "" _int256(const char*);
constexpr integer<512> operator "" _int512(const char*);

template <size_t Bits> std::string to_string(const integer<Bits>&);
template <size_t Bits> std::string to_wstring(const integer<Bits>&);

// ... numeric_limits<integer<Bits> > specializations, ostream/istream
functions, math functions and so on...



Just notifying to avoid duplication of efforts. Is there anyone
already working on that idea?


--
Best regards,
Antony Polukhin

--
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/CAKqmYPaLwFoLf_Vt4KYG9KUB20zVr-anMGRS1JqYaGAjYTaD1A%40mail.gmail.com.

.

--001a11447fce68f58b053ecd9f66
Content-Type: text/plain; charset=UTF-8

Hi Antony,

Yes. There are two topics here.

Firstly, going beyond `int64_t` is something I'd certainly like to see as a
standard language feature. For 64-bit architectures, GCC and Clang support
`__int128` which is a non-standard built-in 128-bit integer type.
Alternatively, there are library-based types which extend beyond 64-bits
such as Boost.Multiprecision.

Secondly, there is a desire to specify integers by their width in bits. I
have a proposal along these lines (
https://github.com/johnmcfarlane/fixed_point/blob/master/doc/p0381.md).
There are other libraries and suggestions which are more like your
`integer<128>`. Mine is a little more extensible for reasons that are
touched upon in P0381.

I would not recommend defining aliases such as `int128_t` for your
`integer<>` types. Those should be reserved for future built-in integer
types. And I don't think they need to be powers of two. I'm sure someone
somewhere would appreciate, say, a 768-bit integer!

I personally have been considering working on something pretty similar to
your `integer<int Bits, bool IsSigned>` class template. Instead of `bool
IsSigned`, it would take a 'class Archetype' - a type that hints at the
underlying type to be used to store the value. Type, `integer<16, signed>`
would provide a type with the same behavior and performance characteristics
of `int16_t`. But `integer<217, unsigned>` would be more complex - perhaps
an array of four `uint64_t` elements or seven `uint32_t` elements -
whichever is more efficient.

Such a type would in turn be used as the basis for other numeric types such
as the `fixed_point<>` proposal I'm also working on:
https://github.com/johnmcfarlane/fixed_point/blob/master/doc/p0037.md

Cheers,
John

On Thu, Oct 13, 2016 at 11:02 PM, Antony Polukhin <antoshkka@gmail.com>
wrote:

> Hello,
>
> Me and a few other people in Russia wish to add extended integer types
> to the C++ Standard (like int128, int256...).
>
> It looks possible to implement that idea as a library only solution.
> The interface will be close to this:
>
> // Class for extended integer types
> template <size_t Bits, bool IsSigned = true>
> class integer {
>     static_assert(is_power_of_2(Bits), "");
>     // ...
>     // all the arithmetic and comparison operators
>     // ...
> };
>
> using int128_t = integer<128>;
> using int256_t = integer<256>;
> using int512_t = integer<512>;
>
> constexpr integer<128> operator "" _int128(const char*);
> constexpr integer<256> operator "" _int256(const char*);
> constexpr integer<512> operator "" _int512(const char*);
>
> template <size_t Bits> std::string to_string(const integer<Bits>&);
> template <size_t Bits> std::string to_wstring(const integer<Bits>&);
>
> // ... numeric_limits<integer<Bits> > specializations, ostream/istream
> functions, math functions and so on...
>
>
>
> Just notifying to avoid duplication of efforts. Is there anyone
> already working on that idea?
>
>
> --
> Best regards,
> Antony Polukhin
>
> --
> 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/CAKqmYPaLwFoLf_Vt4KYG9KUB20zVr-
> anMGRS1JqYaGAjYTaD1A%40mail.gmail.com.
>

--
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/CABPJVnTfjorV9-tnY%3DN9dTuudJ_ttWu_VUKDcjXjgAZMrDiZ8A%40mail.gmail.com.

--001a11447fce68f58b053ecd9f66
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div><div>Hi Antony,<br><br>Yes. There are two topics here=
..<br><br></div>Firstly, going beyond `int64_t` is something I&#39;d certain=
ly like to see as a standard language feature. For 64-bit architectures, GC=
C and Clang support `__int128` which is a non-standard built-in 128-bit int=
eger type. Alternatively, there are library-based types which extend beyond=
 64-bits such as Boost.Multiprecision.<br><br></div><div>Secondly, there is=
 a desire to specify integers by their width in bits. I have a proposal alo=
ng these lines (<a href=3D"https://github.com/johnmcfarlane/fixed_point/blo=
b/master/doc/p0381.md">https://github.com/johnmcfarlane/fixed_point/blob/ma=
ster/doc/p0381.md</a>). There are other libraries and suggestions which are=
 more like your `integer&lt;128&gt;`. Mine is a little more extensible for =
reasons that are touched upon in P0381.<br><br></div><div>I would not recom=
mend defining aliases such as `int128_t` for your `integer&lt;&gt;` types. =
Those should be reserved for future built-in integer types. And I don&#39;t=
 think they need to be powers of two. I&#39;m sure someone somewhere would =
appreciate, say, a 768-bit integer!<br><br>I personally have been consideri=
ng working on something pretty similar to your `integer&lt;int Bits, bool I=
sSigned&gt;` class template. Instead of `bool IsSigned`, it would take a &#=
39;class Archetype&#39; - a type that hints at the underlying type to be us=
ed to store the value. Type, `integer&lt;16, signed&gt;` would provide a ty=
pe with the same behavior and performance characteristics of `int16_t`. But=
 `integer&lt;217, unsigned&gt;` would be more complex - perhaps an array of=
 four `uint64_t` elements or seven `uint32_t` elements - whichever is more =
efficient.<br><br></div><div>Such a type would in turn be used as the basis=
 for other numeric types such as the `fixed_point&lt;&gt;` proposal I&#39;m=
 also working on: <a href=3D"https://github.com/johnmcfarlane/fixed_point/b=
lob/master/doc/p0037.md">https://github.com/johnmcfarlane/fixed_point/blob/=
master/doc/p0037.md</a><br><br></div><div>Cheers,<br></div><div>John<br></d=
iv></div><div class=3D"gmail_extra"><br><div class=3D"gmail_quote">On Thu, =
Oct 13, 2016 at 11:02 PM, Antony Polukhin <span dir=3D"ltr">&lt;<a href=3D"=
mailto:antoshkka@gmail.com" target=3D"_blank">antoshkka@gmail.com</a>&gt;</=
span> wrote:<br><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8e=
x;border-left:1px #ccc solid;padding-left:1ex">Hello,<br>
<br>
Me and a few other people in Russia wish to add extended integer types<br>
to the C++ Standard (like int128, int256...).<br>
<br>
It looks possible to implement that idea as a library only solution.<br>
The interface will be close to this:<br>
<br>
// Class for extended integer types<br>
template &lt;size_t Bits, bool IsSigned =3D true&gt;<br>
class integer {<br>
=C2=A0 =C2=A0 static_assert(is_power_of_2(<wbr>Bits), &quot;&quot;);<br>
=C2=A0 =C2=A0 // ...<br>
=C2=A0 =C2=A0 // all the arithmetic and comparison operators<br>
=C2=A0 =C2=A0 // ...<br>
};<br>
<br>
using int128_t =3D integer&lt;128&gt;;<br>
using int256_t =3D integer&lt;256&gt;;<br>
using int512_t =3D integer&lt;512&gt;;<br>
<br>
constexpr integer&lt;128&gt; operator &quot;&quot; _int128(const char*);<br=
>
constexpr integer&lt;256&gt; operator &quot;&quot; _int256(const char*);<br=
>
constexpr integer&lt;512&gt; operator &quot;&quot; _int512(const char*);<br=
>
<br>
template &lt;size_t Bits&gt; std::string to_string(const integer&lt;Bits&gt=
;&amp;);<br>
template &lt;size_t Bits&gt; std::string to_wstring(const integer&lt;Bits&g=
t;&amp;);<br>
<br>
// ... numeric_limits&lt;integer&lt;Bits&gt; &gt; specializations, ostream/=
istream<br>
functions, math functions and so on...<br>
<br>
<br>
<br>
Just notifying to avoid duplication of efforts. Is there anyone<br>
already working on that idea?<br>
<span class=3D"HOEnZb"><font color=3D"#888888"><br>
<br>
--<br>
Best regards,<br>
Antony Polukhin<br>
<br>
--<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%2Bunsubscribe@isocpp.org">std-propo=
sals+unsubscribe@<wbr>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/CAKqmYPaLwFoLf_Vt4KYG9KUB20zVr-anMGRS=
1JqYaGAjYTaD1A%40mail.gmail.com" rel=3D"noreferrer" target=3D"_blank">https=
://groups.google.com/a/<wbr>isocpp.org/d/msgid/std-<wbr>proposals/CAKqmYPaL=
wFoLf_<wbr>Vt4KYG9KUB20zVr-<wbr>anMGRS1JqYaGAjYTaD1A%40mail.<wbr>gmail.com<=
/a>.<br>
</font></span></blockquote></div><br></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/CABPJVnTfjorV9-tnY%3DN9dTuudJ_ttWu_VU=
KDcjXjgAZMrDiZ8A%40mail.gmail.com?utm_medium=3Demail&utm_source=3Dfooter">h=
ttps://groups.google.com/a/isocpp.org/d/msgid/std-proposals/CABPJVnTfjorV9-=
tnY%3DN9dTuudJ_ttWu_VUKDcjXjgAZMrDiZ8A%40mail.gmail.com</a>.<br />

--001a11447fce68f58b053ecd9f66--

.

--001a11443616b78438053ed18159
Content-Type: text/plain; charset=UTF-8

There is also
https://mail.google.com/mail/u/0/#label/cxx%2Fstd-proposals/15700936ad39e99a

On Fri, Oct 14, 2016 at 9:49 AM, John McFarlane <john@mcfarlane.name> wrote:

> Hi Antony,
>
> Yes. There are two topics here.
>
> Firstly, going beyond `int64_t` is something I'd certainly like to see as
> a standard language feature. For 64-bit architectures, GCC and Clang
> support `__int128` which is a non-standard built-in 128-bit integer type.
> Alternatively, there are library-based types which extend beyond 64-bits
> such as Boost.Multiprecision.
>
> Secondly, there is a desire to specify integers by their width in bits. I
> have a proposal along these lines (https://github.com/
> johnmcfarlane/fixed_point/blob/master/doc/p0381.md). There are other
> libraries and suggestions which are more like your `integer<128>`. Mine is
> a little more extensible for reasons that are touched upon in P0381.
>
> I would not recommend defining aliases such as `int128_t` for your
> `integer<>` types. Those should be reserved for future built-in integer
> types. And I don't think they need to be powers of two. I'm sure someone
> somewhere would appreciate, say, a 768-bit integer!
>
> I personally have been considering working on something pretty similar to
> your `integer<int Bits, bool IsSigned>` class template. Instead of `bool
> IsSigned`, it would take a 'class Archetype' - a type that hints at the
> underlying type to be used to store the value. Type, `integer<16, signed>`
> would provide a type with the same behavior and performance characteristics
> of `int16_t`. But `integer<217, unsigned>` would be more complex - perhaps
> an array of four `uint64_t` elements or seven `uint32_t` elements -
> whichever is more efficient.
>
> Such a type would in turn be used as the basis for other numeric types
> such as the `fixed_point<>` proposal I'm also working on:
> https://github.com/johnmcfarlane/fixed_point/blob/master/doc/p0037.md
>
> Cheers,
> John
>
> On Thu, Oct 13, 2016 at 11:02 PM, Antony Polukhin <antoshkka@gmail.com>
> wrote:
>
>> Hello,
>>
>> Me and a few other people in Russia wish to add extended integer types
>> to the C++ Standard (like int128, int256...).
>>
>> It looks possible to implement that idea as a library only solution.
>> The interface will be close to this:
>>
>> // Class for extended integer types
>> template <size_t Bits, bool IsSigned = true>
>> class integer {
>>     static_assert(is_power_of_2(Bits), "");
>>     // ...
>>     // all the arithmetic and comparison operators
>>     // ...
>> };
>>
>> using int128_t = integer<128>;
>> using int256_t = integer<256>;
>> using int512_t = integer<512>;
>>
>> constexpr integer<128> operator "" _int128(const char*);
>> constexpr integer<256> operator "" _int256(const char*);
>> constexpr integer<512> operator "" _int512(const char*);
>>
>> template <size_t Bits> std::string to_string(const integer<Bits>&);
>> template <size_t Bits> std::string to_wstring(const integer<Bits>&);
>>
>> // ... numeric_limits<integer<Bits> > specializations, ostream/istream
>> functions, math functions and so on...
>>
>>
>>
>> Just notifying to avoid duplication of efforts. Is there anyone
>> already working on that idea?
>>
>>
>> --
>> Best regards,
>> Antony Polukhin
>>
>> --
>> 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/is
>> ocpp.org/d/msgid/std-proposals/CAKqmYPaLwFoLf_Vt4KYG9KUB20zV
>> r-anMGRS1JqYaGAjYTaD1A%40mail.gmail.com.
>>
>
> --
> 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/CABPJVnTfjorV9-tnY%3DN9dTuudJ_ttWu_
> VUKDcjXjgAZMrDiZ8A%40mail.gmail.com
> <https://groups.google.com/a/isocpp.org/d/msgid/std-proposals/CABPJVnTfjorV9-tnY%3DN9dTuudJ_ttWu_VUKDcjXjgAZMrDiZ8A%40mail.gmail.com?utm_medium=email&utm_source=footer>
> .
>



--
Regads,
   Mikhail Maltsev

--
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/CAOqAUTiYaTdWvJgpKX%3DaswqAKT6aDzyHapqBGqsHGXgqJQRnLg%40mail.gmail.com.

--001a11443616b78438053ed18159
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div class=3D"gmail_default" style=3D"font-family:monospac=
e,monospace">There is also=C2=A0<a href=3D"https://mail.google.com/mail/u/0=
/#label/cxx%2Fstd-proposals/15700936ad39e99a">https://mail.google.com/mail/=
u/0/#label/cxx%2Fstd-proposals/15700936ad39e99a</a></div></div><div class=
=3D"gmail_extra"><br><div class=3D"gmail_quote">On Fri, Oct 14, 2016 at 9:4=
9 AM, John McFarlane <span dir=3D"ltr">&lt;<a href=3D"mailto:john@mcfarlane=
..name" target=3D"_blank">john@mcfarlane.name</a>&gt;</span> wrote:<br><bloc=
kquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #cc=
c solid;padding-left:1ex"><div dir=3D"ltr"><div><div>Hi Antony,<br><br>Yes.=
 There are two topics here.<br><br></div>Firstly, going beyond `int64_t` is=
 something I&#39;d certainly like to see as a standard language feature. Fo=
r 64-bit architectures, GCC and Clang support `__int128` which is a non-sta=
ndard built-in 128-bit integer type. Alternatively, there are library-based=
 types which extend beyond 64-bits such as Boost.Multiprecision.<br><br></d=
iv><div>Secondly, there is a desire to specify integers by their width in b=
its. I have a proposal along these lines (<a href=3D"https://github.com/joh=
nmcfarlane/fixed_point/blob/master/doc/p0381.md" target=3D"_blank">https://=
github.com/<wbr>johnmcfarlane/fixed_point/<wbr>blob/master/doc/p0381.md</a>=
). There are other libraries and suggestions which are more like your `inte=
ger&lt;128&gt;`. Mine is a little more extensible for reasons that are touc=
hed upon in P0381.<br><br></div><div>I would not recommend defining aliases=
 such as `int128_t` for your `integer&lt;&gt;` types. Those should be reser=
ved for future built-in integer types. And I don&#39;t think they need to b=
e powers of two. I&#39;m sure someone somewhere would appreciate, say, a 76=
8-bit integer!<br><br>I personally have been considering working on somethi=
ng pretty similar to your `integer&lt;int Bits, bool IsSigned&gt;` class te=
mplate. Instead of `bool IsSigned`, it would take a &#39;class Archetype&#3=
9; - a type that hints at the underlying type to be used to store the value=
.. Type, `integer&lt;16, signed&gt;` would provide a type with the same beha=
vior and performance characteristics of `int16_t`. But `integer&lt;217, uns=
igned&gt;` would be more complex - perhaps an array of four `uint64_t` elem=
ents or seven `uint32_t` elements - whichever is more efficient.<br><br></d=
iv><div>Such a type would in turn be used as the basis for other numeric ty=
pes such as the `fixed_point&lt;&gt;` proposal I&#39;m also working on: <a =
href=3D"https://github.com/johnmcfarlane/fixed_point/blob/master/doc/p0037.=
md" target=3D"_blank">https://github.com/<wbr>johnmcfarlane/fixed_point/<wb=
r>blob/master/doc/p0037.md</a><br><br></div><div>Cheers,<br></div><div>John=
<br></div></div><div><div class=3D"h5"><div class=3D"gmail_extra"><br><div =
class=3D"gmail_quote">On Thu, Oct 13, 2016 at 11:02 PM, Antony Polukhin <sp=
an dir=3D"ltr">&lt;<a href=3D"mailto:antoshkka@gmail.com" target=3D"_blank"=
>antoshkka@gmail.com</a>&gt;</span> wrote:<br><blockquote class=3D"gmail_qu=
ote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex=
">Hello,<br>
<br>
Me and a few other people in Russia wish to add extended integer types<br>
to the C++ Standard (like int128, int256...).<br>
<br>
It looks possible to implement that idea as a library only solution.<br>
The interface will be close to this:<br>
<br>
// Class for extended integer types<br>
template &lt;size_t Bits, bool IsSigned =3D true&gt;<br>
class integer {<br>
=C2=A0 =C2=A0 static_assert(is_power_of_2(Bi<wbr>ts), &quot;&quot;);<br>
=C2=A0 =C2=A0 // ...<br>
=C2=A0 =C2=A0 // all the arithmetic and comparison operators<br>
=C2=A0 =C2=A0 // ...<br>
};<br>
<br>
using int128_t =3D integer&lt;128&gt;;<br>
using int256_t =3D integer&lt;256&gt;;<br>
using int512_t =3D integer&lt;512&gt;;<br>
<br>
constexpr integer&lt;128&gt; operator &quot;&quot; _int128(const char*);<br=
>
constexpr integer&lt;256&gt; operator &quot;&quot; _int256(const char*);<br=
>
constexpr integer&lt;512&gt; operator &quot;&quot; _int512(const char*);<br=
>
<br>
template &lt;size_t Bits&gt; std::string to_string(const integer&lt;Bits&gt=
;&amp;);<br>
template &lt;size_t Bits&gt; std::string to_wstring(const integer&lt;Bits&g=
t;&amp;);<br>
<br>
// ... numeric_limits&lt;integer&lt;Bits&gt; &gt; specializations, ostream/=
istream<br>
functions, math functions and so on...<br>
<br>
<br>
<br>
Just notifying to avoid duplication of efforts. Is there anyone<br>
already working on that idea?<br>
<span class=3D"m_-4042909227987984657HOEnZb"><font color=3D"#888888"><br>
<br>
--<br>
Best regards,<br>
Antony Polukhin<br>
<br>
--<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%2Bunsubscribe@isocpp.org" target=3D=
"_blank">std-proposals+unsubscribe@isoc<wbr>pp.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/CAKqmYPaLwFoLf_Vt4KYG9KUB20zVr-anMGRS=
1JqYaGAjYTaD1A%40mail.gmail.com" rel=3D"noreferrer" target=3D"_blank">https=
://groups.google.com/a/is<wbr>ocpp.org/d/msgid/std-proposals<wbr>/CAKqmYPaL=
wFoLf_Vt4KYG9KUB20zV<wbr>r-anMGRS1JqYaGAjYTaD1A%40mail.<wbr>gmail.com</a>.<=
br>
</font></span></blockquote></div><br></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@<wbr>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></div></div>
To view this discussion on the web visit <a href=3D"https://groups.google.c=
om/a/isocpp.org/d/msgid/std-proposals/CABPJVnTfjorV9-tnY%3DN9dTuudJ_ttWu_VU=
KDcjXjgAZMrDiZ8A%40mail.gmail.com?utm_medium=3Demail&amp;utm_source=3Dfoote=
r" target=3D"_blank">https://groups.google.com/a/<wbr>isocpp.org/d/msgid/st=
d-<wbr>proposals/CABPJVnTfjorV9-tnY%<wbr>3DN9dTuudJ_ttWu_<wbr>VUKDcjXjgAZMr=
DiZ8A%40mail.<wbr>gmail.com</a>.<br>
</blockquote></div><br><br clear=3D"all"><div><br></div>-- <br><div class=
=3D"gmail_signature" data-smartmail=3D"gmail_signature"><div dir=3D"ltr">Re=
gads,<div>=C2=A0 =C2=A0Mikhail Maltsev</div></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/CAOqAUTiYaTdWvJgpKX%3DaswqAKT6aDzyHap=
qBGqsHGXgqJQRnLg%40mail.gmail.com?utm_medium=3Demail&utm_source=3Dfooter">h=
ttps://groups.google.com/a/isocpp.org/d/msgid/std-proposals/CAOqAUTiYaTdWvJ=
gpKX%3DaswqAKT6aDzyHapqBGqsHGXgqJQRnLg%40mail.gmail.com</a>.<br />

--001a11443616b78438053ed18159--

.

--089e01228c124889ed053ed1cc3b
Content-Type: text/plain; charset=UTF-8

On Fri, Oct 14, 2016 at 12:27 PM, Mikhail Maltsev <maltsevm@gmail.com>
wrote:

> There is also https://mail.google.com/mail/u/0/#label/cxx%2Fstd-
> proposals/15700936ad39e99a
>
>
That link won't work for us, unless we hack into your GMail. ;-)

--
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/CACGiwhHB3GCiHqUmdUAzfrMWHmmkzu8qQotKRjktry007doxrQ%40mail.gmail.com.

--089e01228c124889ed053ed1cc3b
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div class=3D"gmail_extra"><div class=3D"gmail_quote">On F=
ri, Oct 14, 2016 at 12:27 PM, Mikhail Maltsev <span dir=3D"ltr">&lt;<a href=
=3D"mailto:maltsevm@gmail.com" target=3D"_blank">maltsevm@gmail.com</a>&gt;=
</span> wrote:<br><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .=
8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir=3D"ltr"><div styl=
e=3D"font-family:monospace,monospace">There is also=C2=A0<a href=3D"https:/=
/mail.google.com/mail/u/0/#label/cxx%2Fstd-proposals/15700936ad39e99a" targ=
et=3D"_blank">https://mail.google.com/<wbr>mail/u/0/#label/cxx%2Fstd-<wbr>p=
roposals/15700936ad39e99a</a></div></div><br></blockquote><div><br></div><d=
iv>That link won&#39;t work for us, unless we hack into your GMail. ;-)<br>=
=C2=A0<br></div></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/CACGiwhHB3GCiHqUmdUAzfrMWHmmkzu8qQotK=
Rjktry007doxrQ%40mail.gmail.com?utm_medium=3Demail&utm_source=3Dfooter">htt=
ps://groups.google.com/a/isocpp.org/d/msgid/std-proposals/CACGiwhHB3GCiHqUm=
dUAzfrMWHmmkzu8qQotKRjktry007doxrQ%40mail.gmail.com</a>.<br />

--089e01228c124889ed053ed1cc3b--

.

--047d7bd9111a1ce594053ed27236
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

On Fri, Oct 14, 2016 at 2:47 PM, D. B. <db0451@gmail.com> wrote:

> On Fri, Oct 14, 2016 at 12:27 PM, Mikhail Maltsev <maltsevm@gmail.com>
> wrote:
>
>> There is also https://mail.google.com/mail/u/0/#label/cxx%2Fstd-propo
>> sals/15700936ad39e99a
>>
>>
> That link won't work for us, unless we hack into your GMail. ;-)
>
> =E2=80=8BOops... Here is the correct link:
=E2=80=8B=E2=80=8B
https://groups.google.com/a/isocpp.org/forum/#!msg/std-proposals/xuX3aTyi3M=
c/aNJSsVFIFAAJ

--=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/CAOqAUTiLNai1K6A2_ip%2BHLz6XmL95SJk2%2BDKOMGD26o=
wN0uUbQ%40mail.gmail.com.

--047d7bd9111a1ce594053ed27236
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div class=3D"gmail_default" style=3D"font-family:monospac=
e,monospace"><span style=3D"font-family:arial,sans-serif">On Fri, Oct 14, 2=
016 at 2:47 PM, D. B. </span><span dir=3D"ltr" style=3D"font-family:arial,s=
ans-serif">&lt;<a href=3D"mailto:db0451@gmail.com" target=3D"_blank">db0451=
@gmail.com</a>&gt;</span><span style=3D"font-family:arial,sans-serif"> wrot=
e:</span><br></div><div class=3D"gmail_extra"><div class=3D"gmail_quote"><b=
lockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-le=
ft-width:1px;border-left-style:solid;border-left-color:rgb(204,204,204);pad=
ding-left:1ex"><div dir=3D"ltr"><div class=3D"gmail_extra"><div class=3D"gm=
ail_quote"><span class=3D"gmail-">On Fri, Oct 14, 2016 at 12:27 PM, Mikhail=
 Maltsev <span dir=3D"ltr">&lt;<a href=3D"mailto:maltsevm@gmail.com" target=
=3D"_blank">maltsevm@gmail.com</a>&gt;</span> wrote:<br><blockquote class=
=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-left-width:1px;bo=
rder-left-style:solid;border-left-color:rgb(204,204,204);padding-left:1ex">=
<div dir=3D"ltr"><div style=3D"font-family:monospace,monospace">There is al=
so=C2=A0<a href=3D"https://mail.google.com/mail/u/0/#label/cxx%2Fstd-propos=
als/15700936ad39e99a" target=3D"_blank">https://mail.google.com/m<wbr>ail/u=
/0/#label/cxx%2Fstd-propo<wbr>sals/15700936ad39e99a</a></div></div><br></bl=
ockquote><div><br></div></span><div>That link won&#39;t work for us, unless=
 we hack into your GMail. ;-)<br><br></div></div></div></div></blockquote><=
div><div class=3D"gmail_default" style=3D"font-family:monospace,monospace;d=
isplay:inline">=E2=80=8BOops... Here is the correct link:</div></div><div><=
font face=3D"monospace, monospace"><div class=3D"gmail_default" style=3D"fo=
nt-family:monospace,monospace;display:inline">=E2=80=8B=E2=80=8B</div><a hr=
ef=3D"https://groups.google.com/a/isocpp.org/forum/#!msg/std-proposals/xuX3=
aTyi3Mc/aNJSsVFIFAAJ">https://groups.google.com/a/isocpp.org/forum/#!msg/st=
d-proposals/xuX3aTyi3Mc/aNJSsVFIFAAJ</a></font><br></div></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/CAOqAUTiLNai1K6A2_ip%2BHLz6XmL95SJk2%=
2BDKOMGD26owN0uUbQ%40mail.gmail.com?utm_medium=3Demail&utm_source=3Dfooter"=
>https://groups.google.com/a/isocpp.org/d/msgid/std-proposals/CAOqAUTiLNai1=
K6A2_ip%2BHLz6XmL95SJk2%2BDKOMGD26owN0uUbQ%40mail.gmail.com</a>.<br />

--047d7bd9111a1ce594053ed27236--

.