------=_Part_217_1295025253.1455984771575
Content-Type: multipart/alternative;
 boundary="----=_Part_218_1127708182.1455984771575"

------=_Part_218_1127708182.1455984771575
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

Hi,

It seems that the proposal in its current version ([1]) is incomplete =E2=
=80=93=20
even if it makes aliasing by std::byte allowed, casting to std::byte* from=
=20
an allocated storage is still UB according to 3.8/5.4. Other places that=20
deal with object byte representation are 3.9/2 (round-trip guarantee for=20
copying objects into byte arrays) and 5.3.4/11 (alignment of byte arrays=20
allocated with new). Therefore I suggest the author also modifies those=20
paragraphs accordingly.

Best regards,
Robert

[1] http://open-std.org/JTC1/SC22/WG21/docs/papers/2016/p0257r0.pdf

--=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/744345b9-ac92-4b30-aa42-bb5324497b9d%40isocpp.or=
g.

------=_Part_218_1127708182.1455984771575
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div>Hi,<br></div><div><br></div><div>It seems that the pr=
oposal in its current version ([1]) is incomplete =E2=80=93 even if it make=
s aliasing by std::byte allowed, casting to std::byte* from an allocated st=
orage is still UB according to 3.8/5.4. Other places that deal with object =
byte representation are 3.9/2 (round-trip guarantee for copying objects int=
o byte arrays) and 5.3.4/11 (alignment of byte arrays allocated with new). =
Therefore I suggest the author also modifies those paragraphs accordingly.<=
/div><div><br></div><div>Best regards,</div><div>Robert</div><div><br></div=
><div>[1] http://open-std.org/JTC1/SC22/WG21/docs/papers/2016/p0257r0.pdf</=
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/744345b9-ac92-4b30-aa42-bb5324497b9d%=
40isocpp.org?utm_medium=3Demail&utm_source=3Dfooter">https://groups.google.=
com/a/isocpp.org/d/msgid/std-proposals/744345b9-ac92-4b30-aa42-bb5324497b9d=
%40isocpp.org</a>.<br />

------=_Part_218_1127708182.1455984771575--
------=_Part_217_1295025253.1455984771575--

.

On 02/20/2016 05:12 PM, Robert wrote:
> Hi,
>=20
> It seems that the proposal in its current version ([1]) is incomplete =E2=
=80=93 even if it makes aliasing by std::byte allowed, casting to std::byte=
* from an allocated storage is still UB according to 3.8/5.4. Other places =
that deal with object byte representation are 3.9/2 (round-trip guarantee f=
or copying objects into byte arrays) and 5.3.4/11 (alignment of byte arrays=
 allocated with new). Therefore I suggest the author also modifies those pa=
ragraphs accordingly.

.... at which point it becomes an EWG / CWG proposal in
addition to L(E)WG.

Jens

--=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/56C98887.70604%40gmx.net.

.

On Sat, Feb 20, 2016 at 10:12 AM, Robert <robert.kawulak@gmail.com> wrote:
> Therefore I suggest the author also modifies those paragraphs accordingly.
>
> Best regards,
> Robert
>
> [1] http://open-std.org/JTC1/SC22/WG21/docs/papers/2016/p0257r0.pdf

I have two problems with this proposal:

  1. Introducing a new type to represent bytes invites template
      code bloat.
  2. Introducing a vocabulary type work like a fundamental type
      but not exists in C reduces the interoperability between C
      and C++.

--
Zhihao Yuan, ID lichray
The best way to predict the future is to invent it.
___________________________________________________
4BSD -- http://bit.ly/blog4bsd

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

.

Jens Maurer, 2016-02-21 10:51:03:
> ... at which point it becomes an EWG / CWG proposal in
> addition to L(E)WG.

It already is an EWG proposal.

--
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/!%26!AAAAAAAAAAAYAAAAAAAAAP2My3EH4FhKr%2BL7Y/eBBJTigAAAEAAAAO1z09PvUyxIkwPwjoXPB3cBAAAAAA%3D%3D%40gmail.com.

.

--047d7bd91b7eb4eae0052c4a1494
Content-Type: text/plain; charset=UTF-8

I think that we should have a bit type. I know that we have a Boolean type,
yet it does not fit when I am trying to write to initialization registers
on a chip.

I understand byte alignment is more efficient, yet to allocate a byte, then
mask it into another byte seems like extra code bloat.

That is my opinion.

Brett

On Sun, Feb 21, 2016 at 6:40 AM, Robert Kawulak <robert.kawulak@gmail.com>
wrote:

> Jens Maurer, 2016-02-21 10:51:03:
> > ... at which point it becomes an EWG / CWG proposal in
> > addition to L(E)WG.
>
> It already is an EWG proposal.
>
> --
> 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/!%26!AAAAAAAAAAAYAAAAAAAAAP2My3EH4FhKr%2BL7Y/eBBJTigAAAEAAAAO1z09PvUyxIkwPwjoXPB3cBAAAAAA%3D%3D%40gmail.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/CAN1bbVLEbbATYa_wF4YiKX1tk7c_z2Ax-uWmrTotk1cx2qno1A%40mail.gmail.com.

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

<div dir=3D"ltr"><div>I think that we should have a bit type. I know that w=
e have a Boolean type, yet it does not fit when I am trying to write to ini=
tialization registers on a chip. </div><div><br></div><div>I understand byt=
e alignment is more efficient, yet to allocate a byte, then mask it into an=
other byte seems like extra code bloat.</div><div><br></div><div>That is my=
 opinion.</div><div><br></div><div>Brett</div></div><div class=3D"gmail_ext=
ra"><br><div class=3D"gmail_quote">On Sun, Feb 21, 2016 at 6:40 AM, Robert =
Kawulak <span dir=3D"ltr">&lt;<a href=3D"mailto:robert.kawulak@gmail.com" t=
arget=3D"_blank">robert.kawulak@gmail.com</a>&gt;</span> wrote:<br><blockqu=
ote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc s=
olid;padding-left:1ex">Jens Maurer, 2016-02-21 10:51:03:<br>
<span>&gt; ... at which point it becomes an EWG / CWG proposal in<br>
&gt; addition to L(E)WG.<br>
<br>
</span>It already is an EWG proposal.<br>
<span><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@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>
</span>To view this discussion on the web visit <a href=3D"https://groups.g=
oogle.com/a/isocpp.org/d/msgid/std-proposals/!%26!AAAAAAAAAAAYAAAAAAAAAP2My=
3EH4FhKr%2BL7Y/eBBJTigAAAEAAAAO1z09PvUyxIkwPwjoXPB3cBAAAAAA%3D%3D%40gmail.c=
om" target=3D"_blank" rel=3D"noreferrer">https://groups.google.com/a/isocpp=
..org/d/msgid/std-proposals/!%26!AAAAAAAAAAAYAAAAAAAAAP2My3EH4FhKr%2BL7Y/eBB=
JTigAAAEAAAAO1z09PvUyxIkwPwjoXPB3cBAAAAAA%3D%3D%40gmail.com</a>.<br>
</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/CAN1bbVLEbbATYa_wF4YiKX1tk7c_z2Ax-uWm=
rTotk1cx2qno1A%40mail.gmail.com?utm_medium=3Demail&utm_source=3Dfooter">htt=
ps://groups.google.com/a/isocpp.org/d/msgid/std-proposals/CAN1bbVLEbbATYa_w=
F4YiKX1tk7c_z2Ax-uWmrTotk1cx2qno1A%40mail.gmail.com</a>.<br />

--047d7bd91b7eb4eae0052c4a1494--

.

------=_Part_146_240701829.1456332922387
Content-Type: multipart/alternative;
 boundary="----=_Part_147_269706610.1456332922387"

------=_Part_147_269706610.1456332922387
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

Are you talking about bits or bytes?
For bits, see P0237=20
<http://open-std.org/JTC1/SC22/WG21/docs/papers/2016/p0237r0.pdf> in the=20
mailing (comments are always welcome)

Le dimanche 21 f=C3=A9vrier 2016 10:19:32 UTC-6, Brett Searles a =C3=A9crit=
 :
>
> I think that we should have a bit type. I know that we have a Boolean=20
> type, yet it does not fit when I am trying to write to initialization=20
> registers on a chip.=20
>
> I understand byte alignment is more efficient, yet to allocate a byte,=20
> then mask it into another byte seems like extra code bloat.
>
> That is my opinion.
>
> Brett
>
> On Sun, Feb 21, 2016 at 6:40 AM, Robert Kawulak <robert....@gmail.com=20
> <javascript:>> wrote:
>
>> Jens Maurer, 2016-02-21 10:51:03:
>> > ... at which point it becomes an EWG / CWG proposal in
>> > addition to L(E)WG.
>>
>> It already is an EWG proposal.
>>
>> --
>> You received this message because you are subscribed to the Google Group=
s=20
>> "ISO C++ Standard - Future Proposals" group.
>> To unsubscribe from this group and stop receiving emails from it, send a=
n=20
>> email to std-proposal...@isocpp.org <javascript:>.
>> To post to this group, send email to std-pr...@isocpp.org <javascript:>.
>> To view this discussion on the web visit=20
>> https://groups.google.com/a/isocpp.org/d/msgid/std-proposals/!%26!AAAAAA=
AAAAAYAAAAAAAAAP2My3EH4FhKr%2BL7Y/eBBJTigAAAEAAAAO1z09PvUyxIkwPwjoXPB3cBAAA=
AAA%3D%3D%40gmail.com
>> .
>>
>
>

--=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/9b73d51b-466d-45a2-8eb6-f1fee96b201b%40isocpp.or=
g.

------=_Part_147_269706610.1456332922387
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">Are you talking about bits or bytes?<br>For bits, see <a h=
ref=3D"http://open-std.org/JTC1/SC22/WG21/docs/papers/2016/p0237r0.pdf">P02=
37</a> in the mailing (comments are always welcome)<br><br>Le dimanche 21 f=
=C3=A9vrier 2016 10:19:32 UTC-6, Brett Searles a =C3=A9crit=C2=A0:<blockquo=
te class=3D"gmail_quote" style=3D"margin: 0;margin-left: 0.8ex;border-left:=
 1px #ccc solid;padding-left: 1ex;"><div dir=3D"ltr"><div>I think that we s=
hould have a bit type. I know that we have a Boolean type, yet it does not =
fit when I am trying to write to initialization registers on a chip. </div>=
<div><br></div><div>I understand byte alignment is more efficient, yet to a=
llocate a byte, then mask it into another byte seems like extra code bloat.=
</div><div><br></div><div>That is my opinion.</div><div><br></div><div>Bret=
t</div></div><div><br><div class=3D"gmail_quote">On Sun, Feb 21, 2016 at 6:=
40 AM, Robert Kawulak <span dir=3D"ltr">&lt;<a href=3D"javascript:" target=
=3D"_blank" gdf-obfuscated-mailto=3D"0LKATY1mAQAJ" rel=3D"nofollow" onmouse=
down=3D"this.href=3D&#39;javascript:&#39;;return true;" onclick=3D"this.hre=
f=3D&#39;javascript:&#39;;return true;">robert....@gmail.com</a>&gt;</span>=
 wrote:<br><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;bor=
der-left:1px #ccc solid;padding-left:1ex">Jens Maurer, 2016-02-21 10:51:03:=
<br>
<span>&gt; ... at which point it becomes an EWG / CWG proposal in<br>
&gt; addition to L(E)WG.<br>
<br>
</span>It already is an EWG proposal.<br>
<span><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"javascript:" target=3D"_blank" gdf-obfuscated-mailto=3D"=
0LKATY1mAQAJ" rel=3D"nofollow" onmousedown=3D"this.href=3D&#39;javascript:&=
#39;;return true;" onclick=3D"this.href=3D&#39;javascript:&#39;;return true=
;">std-proposal...@<wbr>isocpp.org</a>.<br>
To post to this group, send email to <a href=3D"javascript:" target=3D"_bla=
nk" gdf-obfuscated-mailto=3D"0LKATY1mAQAJ" rel=3D"nofollow" onmousedown=3D"=
this.href=3D&#39;javascript:&#39;;return true;" onclick=3D"this.href=3D&#39=
;javascript:&#39;;return true;">std-pr...@isocpp.org</a>.<br>
</span>To view this discussion on the web visit <a href=3D"https://groups.g=
oogle.com/a/isocpp.org/d/msgid/std-proposals/!%26!AAAAAAAAAAAYAAAAAAAAAP2My=
3EH4FhKr%2BL7Y/eBBJTigAAAEAAAAO1z09PvUyxIkwPwjoXPB3cBAAAAAA%3D%3D%40gmail.c=
om" rel=3D"nofollow" target=3D"_blank" onmousedown=3D"this.href=3D&#39;http=
s://groups.google.com/a/isocpp.org/d/msgid/std-proposals/!%26!AAAAAAAAAAAYA=
AAAAAAAAP2My3EH4FhKr%2BL7Y/eBBJTigAAAEAAAAO1z09PvUyxIkwPwjoXPB3cBAAAAAA%3D%=
3D%40gmail.com&#39;;return true;" onclick=3D"this.href=3D&#39;https://group=
s.google.com/a/isocpp.org/d/msgid/std-proposals/!%26!AAAAAAAAAAAYAAAAAAAAAP=
2My3EH4FhKr%2BL7Y/eBBJTigAAAEAAAAO1z09PvUyxIkwPwjoXPB3cBAAAAAA%3D%3D%40gmai=
l.com&#39;;return true;">https://groups.google.com/a/<wbr>isocpp.org/d/msgi=
d/std-<wbr>proposals/!%26!<wbr>AAAAAAAAAAAYAAAAAAAAAP2My3EH4F<wbr>hKr%2BL7Y=
/<wbr>eBBJTigAAAEAAAAO1z09PvUyxIkwPw<wbr>joXPB3cBAAAAAA%3D%3D%40gmail.<wbr>=
com</a>.<br>
</blockquote></div><br></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/9b73d51b-466d-45a2-8eb6-f1fee96b201b%=
40isocpp.org?utm_medium=3Demail&utm_source=3Dfooter">https://groups.google.=
com/a/isocpp.org/d/msgid/std-proposals/9b73d51b-466d-45a2-8eb6-f1fee96b201b=
%40isocpp.org</a>.<br />

------=_Part_147_269706610.1456332922387--
------=_Part_146_240701829.1456332922387--

.

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

I was talking about bits. Looking at the proposal you linked to in the
reply. Will try to give some feedback soon.

Brett

On Wed, Feb 24, 2016 at 8:55 AM, Vincent Reverdy <vince.rev@gmail.com>
wrote:

> Are you talking about bits or bytes?
> For bits, see P0237
> <http://open-std.org/JTC1/SC22/WG21/docs/papers/2016/p0237r0.pdf> in the
> mailing (comments are always welcome)
>
> Le dimanche 21 f=C3=A9vrier 2016 10:19:32 UTC-6, Brett Searles a =C3=A9cr=
it :
>>
>> I think that we should have a bit type. I know that we have a Boolean
>> type, yet it does not fit when I am trying to write to initialization
>> registers on a chip.
>>
>> I understand byte alignment is more efficient, yet to allocate a byte,
>> then mask it into another byte seems like extra code bloat.
>>
>> That is my opinion.
>>
>> Brett
>>
>> On Sun, Feb 21, 2016 at 6:40 AM, Robert Kawulak <robert....@gmail.com>
>> wrote:
>>
>>> Jens Maurer, 2016-02-21 10:51:03:
>>> > ... at which point it becomes an EWG / CWG proposal in
>>> > addition to L(E)WG.
>>>
>>> It already is an EWG proposal.
>>>
>>> --
>>> 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-proposal...@isocpp.org.
>>> To post to this group, send email to std-pr...@isocpp.org.
>>> To view this discussion on the web visit
>>> https://groups.google.com/a/isocpp.org/d/msgid/std-proposals/!%26!AAAAA=
AAAAAAYAAAAAAAAAP2My3EH4FhKr%2BL7Y/eBBJTigAAAEAAAAO1z09PvUyxIkwPwjoXPB3cBAA=
AAAA%3D%3D%40gmail.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/9b73d51b-466=
d-45a2-8eb6-f1fee96b201b%40isocpp.org
> <https://groups.google.com/a/isocpp.org/d/msgid/std-proposals/9b73d51b-46=
6d-45a2-8eb6-f1fee96b201b%40isocpp.org?utm_medium=3Demail&utm_source=3Dfoot=
er>
> .
>

--=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/CAN1bbVLYB3sV%3DOWeOtE5NYtR_0nmd6OWoHJv32wA%2BSZ=
dK5jCOg%40mail.gmail.com.

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

<div dir=3D"ltr"><div>I was talking about bits. Looking at the proposal you=
 linked to in the reply. Will try to give some feedback soon.</div><div><br=
></div><div>Brett</div></div><div class=3D"gmail_extra"><br><div class=3D"g=
mail_quote">On Wed, Feb 24, 2016 at 8:55 AM, Vincent Reverdy <span dir=3D"l=
tr">&lt;<a href=3D"mailto:vince.rev@gmail.com" target=3D"_blank">vince.rev@=
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">Are you talking about bits or bytes?<br>For bits, see <a href=3D"h=
ttp://open-std.org/JTC1/SC22/WG21/docs/papers/2016/p0237r0.pdf" target=3D"_=
blank">P0237</a> in the mailing (comments are always welcome)<span><br><br>=
Le dimanche 21 f=C3=A9vrier 2016 10:19:32 UTC-6, Brett Searles a =C3=A9crit=
=C2=A0:</span><blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px=
 0.8ex;padding-left:1ex;border-left-color:rgb(204,204,204);border-left-widt=
h:1px;border-left-style:solid"><span><div dir=3D"ltr"><div>I think that we =
should have a bit type. I know that we have a Boolean type, yet it does not=
 fit when I am trying to write to initialization registers on a chip. </div=
><div><br></div><div>I understand byte alignment is more efficient, yet to =
allocate a byte, then mask it into another byte seems like extra code bloat=
..</div><div><br></div><div>That is my opinion.</div><div><br></div><div>Bre=
tt</div></div></span><div><br><div class=3D"gmail_quote"><span>On Sun, Feb =
21, 2016 at 6:40 AM, Robert Kawulak <span dir=3D"ltr">&lt;<a rel=3D"nofollo=
w">robert....@gmail.com</a>&gt;</span> wrote:<br></span><blockquote class=
=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;padding-left:1ex;border-=
left-color:rgb(204,204,204);border-left-width:1px;border-left-style:solid">=
<span>Jens Maurer, 2016-02-21 10:51:03:<br>
<span>&gt; ... at which point it becomes an EWG / CWG proposal in<br>
&gt; addition to L(E)WG.<br>
<br>
</span>It already is an EWG proposal.<br>
</span><span><span><br>
--<br>
You received this message because you are subscribed to the Google Groups &=
quot;ISO C++ Standard - Future Proposals&quot; group.<br></span>
To unsubscribe from this group and stop receiving emails from it, send an e=
mail to <a rel=3D"nofollow">std-proposal...@isocpp.org</a>.<br>
To post to this group, send email to <a rel=3D"nofollow">std-pr...@isocpp.o=
rg</a>.<br>
</span><span>To view this discussion on the web visit <a href=3D"https://gr=
oups.google.com/a/isocpp.org/d/msgid/std-proposals/!%26!AAAAAAAAAAAYAAAAAAA=
AAP2My3EH4FhKr%2BL7Y/eBBJTigAAAEAAAAO1z09PvUyxIkwPwjoXPB3cBAAAAAA%3D%3D%40g=
mail.com" target=3D"_blank" rel=3D"nofollow">https://groups.google.com/a/is=
ocpp.org/d/msgid/std-proposals/!%26!AAAAAAAAAAAYAAAAAAAAAP2My3EH4FhKr%2BL7Y=
/eBBJTigAAAEAAAAO1z09PvUyxIkwPwjoXPB3cBAAAAAA%3D%3D%40gmail.com</a>.<br>
</span></blockquote></div><br></div>
</blockquote></div><span>

<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></span>
To view this discussion on the web visit <a href=3D"https://groups.google.c=
om/a/isocpp.org/d/msgid/std-proposals/9b73d51b-466d-45a2-8eb6-f1fee96b201b%=
40isocpp.org?utm_medium=3Demail&amp;utm_source=3Dfooter" target=3D"_blank">=
https://groups.google.com/a/isocpp.org/d/msgid/std-proposals/9b73d51b-466d-=
45a2-8eb6-f1fee96b201b%40isocpp.org</a>.<br>
</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/CAN1bbVLYB3sV%3DOWeOtE5NYtR_0nmd6OWoH=
Jv32wA%2BSZdK5jCOg%40mail.gmail.com?utm_medium=3Demail&utm_source=3Dfooter"=
>https://groups.google.com/a/isocpp.org/d/msgid/std-proposals/CAN1bbVLYB3sV=
%3DOWeOtE5NYtR_0nmd6OWoHJv32wA%2BSZdK5jCOg%40mail.gmail.com</a>.<br />

--047d7bd91b7e9ef0cb052c9c1cb3--

.