Topic: More conservative version of P0907 "Signed Integers


Author: "Arthur O'Dwyer" <arthur.j.odwyer@gmail.com>
Date: Fri, 23 Feb 2018 14:05:16 -0800
Raw View
--001a114011e202f86b0565e85b42
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

The pre-JAX mailing contains this discussion-provoking paper by JF Bastien:
P0907R0 "Signed Integers are Two's Complement"
<http://www.open-std.org/jtc1/sc22/wg21/docs/papers/2018/p0907r0.html>

My understanding is that JF wants to use this "modest proposal" (for
wrapping arithmetic on `int`, among other things) as a way to incite
discussion among the Committee.

I have created an as-yet-unofficial "conservative fork" of the proposal,
which removes the parts that I think are airballs, while leaving in much of
what I consider the good stuff =E2=80=94 notably, making signed-to-unsigned=
 and
unsigned-to-signed conversions well-defined in terms of two's complement
representations, and defining what happens when you bit-shift into or out
of the sign bit.
https://quuxplusone.github.io/draft/twosc-conservative.html

I hope that if the Committee asks JF to come back with a more conservative
proposal, the existence of my "conservative fork" will save time, possibly
even allow further discussion later in the week at JAX.

I personally will not be at JAX, though.  JF, will you be? Could I count on
you to... not to "champion" my unsubmitted paper, of course, but just to be
aware of it in case something like it is asked for by the Committee?  I
mean, the worst-case, which I would like to avoid, is that JF's paper is
rejected as too crazy and then the entire subject is tabled until
Rapperswil. I would like to see some concrete progress in this department
at JAX if humanly possible.

=E2=80=93Arthur

P.S. =E2=80=94 Also, if anyone on std-proposals has objections to the speci=
fic
diffs in my conservative proposal, I would like to know about it. I
deliberately tried to remove any whiff of controversy from the diff.  (This
is distinct from objecting to my presumptuousness or objecting to wasting
the Committee's time. ;))

--=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/CADvuK0LuUyyHCDhYZ%2BLn2iNuj9WH1bfYrfNoRgD06C5wd=
qW35w%40mail.gmail.com.

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

<div dir=3D"ltr"><div>The pre-JAX mailing contains this discussion-provokin=
g paper by JF Bastien:</div><div><a href=3D"http://www.open-std.org/jtc1/sc=
22/wg21/docs/papers/2018/p0907r0.html">P0907R0 &quot;Signed Integers are Tw=
o&#39;s Complement&quot;</a></div><div><br></div><div>My understanding is t=
hat JF wants to use this &quot;modest proposal&quot; (for wrapping arithmet=
ic on `int`, among other things) as a way to incite discussion among the Co=
mmittee.</div><br><div>I have created an as-yet-unofficial &quot;conservati=
ve fork&quot; of the proposal, which removes the parts that I think are air=
balls, while leaving in much of what I consider the good stuff =E2=80=94 no=
tably, making signed-to-unsigned and unsigned-to-signed conversions well-de=
fined in terms of two&#39;s complement representations, and defining what h=
appens when you bit-shift into or out of the sign bit.</div><div><a href=3D=
"https://quuxplusone.github.io/draft/twosc-conservative.html">https://quuxp=
lusone.github.io/draft/twosc-conservative.html</a><br></div><div><br></div>=
<div>I hope that if the Committee asks JF to come back with a more conserva=
tive proposal, the existence of my &quot;conservative fork&quot; will save =
time, possibly even allow further discussion later in the week at JAX.<br><=
/div><div><br></div><div>I personally will not be at JAX, though.=C2=A0 JF,=
 will you be? Could I count on you to... not to &quot;champion&quot; my uns=
ubmitted paper, of course, but just to be aware of it in case something lik=
e it is asked for by the Committee?=C2=A0 I mean, the worst-case, which I w=
ould like to avoid, is that JF&#39;s paper is rejected as too crazy and the=
n the entire subject is tabled until Rapperswil. I would like to see some c=
oncrete progress in this department at JAX if humanly possible.</div><div><=
br></div><div>=E2=80=93Arthur</div><div><br></div><div>P.S. =E2=80=94 Also,=
 if anyone on std-proposals has objections to the specific diffs in my cons=
ervative proposal, I would like to know about it. I deliberately tried to r=
emove any whiff of controversy from the diff. =C2=A0(This is distinct from =
objecting to my presumptuousness or objecting to wasting the Committee&#39;=
s time. ;))</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/CADvuK0LuUyyHCDhYZ%2BLn2iNuj9WH1bfYrf=
NoRgD06C5wdqW35w%40mail.gmail.com?utm_medium=3Demail&utm_source=3Dfooter">h=
ttps://groups.google.com/a/isocpp.org/d/msgid/std-proposals/CADvuK0LuUyyHCD=
hYZ%2BLn2iNuj9WH1bfYrfNoRgD06C5wdqW35w%40mail.gmail.com</a>.<br />

--001a114011e202f86b0565e85b42--

.