------=_Part_7629_1413949845.1459492243256
Content-Type: multipart/alternative;
 boundary="----=_Part_7630_737799302.1459492243256"

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

I just noticed that the rest of the std::atoi(), std::itoa() and std::iota(=
)=20
family is missing.
I think we need to start an urgent work to be able to include those in=20
C++17 to keep C++ relevant in the modern age.
Was there any thought given to including the rest of the permutations at=20
Jacksonville? I mean the following:

std::aiot()
std::aito()
std::aoit()
std::aoti()
std::atio()
std::iaot()
std::iato()
std::ioat()
std::itao()
std::oait()
std::oati()
std::oiat() =E2=80=93 This one will express a particularly painful part in =
a=20
program.
std::oita()
std::otai()
std::otia()
std::taio()
std::taoi() =E2=80=93 Tactical Area Of Interest, obviously.
std::tiao()
std::tioa()
std::toai() =E2=80=93 This will automatically convert your program into an=
=20
artificial intelligence engine that passes the Turing test.
std::toia()

I am willing to write detailed proposals on all of those, but I'm not sure=
=20
what each in particular should do. Although I do have ideas for a couple=20
there. Suggestions are very welcome.

Have a very nice day.

--=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/b10648e2-bfc5-42db-9742-cb3db41019d4%40isocpp.or=
g.

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

<div dir=3D"ltr">I just noticed that the rest of the <font face=3D"courier =
new, monospace">std::atoi()</font>,<font face=3D"courier new, monospace"> s=
td::itoa()=C2=A0</font>and<font face=3D"courier new, monospace">=C2=A0std::=
iota()</font> family is missing.<div>I think we need to start an urgent wor=
k to be able to include those in C++17 to keep C++ relevant in the modern a=
ge.<div>Was there any thought given to including the rest of the permutatio=
ns at Jacksonville? I mean the following:<br></div><div><br></div><div><div=
><font face=3D"courier new, monospace">std::aiot()</font></div><div><font f=
ace=3D"courier new, monospace">std::aito()</font></div><div><font face=3D"c=
ourier new, monospace">std::aoit()</font></div><div><font face=3D"courier n=
ew, monospace">std::aoti()</font></div><div><font face=3D"courier new, mono=
space">std::atio()</font></div><div><font face=3D"courier new, monospace">s=
td::iaot()</font></div><div><font face=3D"courier new, monospace">std::iato=
()</font></div><div><font face=3D"courier new, monospace">std::ioat()</font=
></div><div><font face=3D"courier new, monospace">std::itao()</font></div><=
div><font face=3D"courier new, monospace">std::oait()</font></div><div><fon=
t face=3D"courier new, monospace">std::oati()</font></div><div><font face=
=3D"courier new, monospace">std::oiat()</font><span style=3D"font-family: a=
rial, sans-serif;">=C2=A0=E2=80=93</span><span style=3D"font-family: arial,=
 sans-serif;">=C2=A0This one will express a particularly painful part in a =
program.</span></div><div><font face=3D"courier new, monospace">std::oita()=
</font></div><div><font face=3D"courier new, monospace">std::otai()</font><=
/div><div><font face=3D"courier new, monospace">std::otia()</font></div><di=
v><font face=3D"courier new, monospace">std::taio()</font></div><div><font =
face=3D"courier new, monospace">std::taoi()</font><span style=3D"font-famil=
y: arial, sans-serif;">=C2=A0=E2=80=93</span><span style=3D"font-family: ar=
ial, sans-serif;">=C2=A0Tactical Area Of Interest, obviously.</span></div><=
div><font face=3D"courier new, monospace">std::tiao()</font></div><div><fon=
t face=3D"courier new, monospace">std::tioa()</font></div><div><font face=
=3D"courier new, monospace">std::toai()</font><font face=3D"arial, sans-ser=
if">=C2=A0=E2=80=93=C2=A0This will automatically convert your program into =
an artificial intelligence engine that passes the Turing test.</font></div>=
<div><font face=3D"courier new, monospace">std::toia()</font></div></div><d=
iv><br></div><div>I am willing to write detailed proposals on all of those,=
 but I&#39;m not sure what each in particular should do. Although I do have=
 ideas for a couple there. Suggestions are very welcome.</div><div><br></di=
v><div>Have a very nice day.</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/b10648e2-bfc5-42db-9742-cb3db41019d4%=
40isocpp.org?utm_medium=3Demail&utm_source=3Dfooter">https://groups.google.=
com/a/isocpp.org/d/msgid/std-proposals/b10648e2-bfc5-42db-9742-cb3db41019d4=
%40isocpp.org</a>.<br />

------=_Part_7630_737799302.1459492243256--
------=_Part_7629_1413949845.1459492243256--

.

On Thu, Mar 31, 2016 at 11:30:43PM -0700, Leo Heinsaar wrote:
> I just noticed that the rest of the std::atoi(), std::itoa() and std::iota()
> family is missing.
> I think we need to start an urgent work to be able to include those in
> C++17 to keep C++ relevant in the modern age.
> Was there any thought given to including the rest of the permutations at
> Jacksonville? I mean the following:
>
....
>
> I am willing to write detailed proposals on all of those, but I'm not sure
> what each in particular should do. Although I do have ideas for a couple
> there. Suggestions are very welcome.

I think you can save yourself an significant bit of work if you write just
std::toai and then uses that to generate proposals for the rest of the
functions.

> Have a very nice day.

/Skynet was here

--
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/20160401071241.GA6991%40noemi.

.

------=_Part_9152_165506651.1459495228836
Content-Type: multipart/alternative;
 boundary="----=_Part_9153_594754598.1459495228837"

------=_Part_9153_594754598.1459495228837
Content-Type: text/plain; charset=UTF-8


>
> > I am willing to write detailed proposals on all of those, but I'm not
> sure
> > what each in particular should do. Although I do have ideas for a couple
> > there. Suggestions are very welcome.
>
> I think you can save yourself an significant bit of work if you write just
> std::toai and then uses that to generate proposals for the rest of the
> functions.
>

Good idea.

> Have a very nice day.
>
> /Skynet was here
>

--
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/33a823b3-ad93-4651-a4d3-19d5b232d597%40isocpp.org.

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

<blockquote class=3D"gmail_quote" style=3D"margin: 0;margin-left: 0.8ex;bor=
der-left: 1px #ccc solid;padding-left: 1ex;">&gt; I am willing to write det=
ailed proposals on all of those, but I&#39;m not sure=20
<br>&gt; what each in particular should do. Although I do have ideas for a =
couple=20
<br>&gt; there. Suggestions are very welcome.
<br>
<br>I think you can save yourself an significant bit of work if you write j=
ust
<br>std::toai and then uses that to generate proposals for the rest of the
<br>functions.
<br></blockquote><div><br></div><div>Good idea.</div><div><br></div><blockq=
uote class=3D"gmail_quote" style=3D"margin: 0;margin-left: 0.8ex;border-lef=
t: 1px #ccc solid;padding-left: 1ex;">&gt; Have a very nice day.
<br>
<br>/Skynet was here
<br></blockquote>

<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/33a823b3-ad93-4651-a4d3-19d5b232d597%=
40isocpp.org?utm_medium=3Demail&utm_source=3Dfooter">https://groups.google.=
com/a/isocpp.org/d/msgid/std-proposals/33a823b3-ad93-4651-a4d3-19d5b232d597=
%40isocpp.org</a>.<br />

------=_Part_9153_594754598.1459495228837--
------=_Part_9152_165506651.1459495228836--

.

On 1 April 2016 at 10:20, Leo Heinsaar <leoheinsaar@gmail.com> wrote:
>> > I am willing to write detailed proposals on all of those, but I'm not
>> > sure
>> > what each in particular should do. Although I do have ideas for a couple
>> > there. Suggestions are very welcome.
>>
>> I think you can save yourself an significant bit of work if you write just
>> std::toai and then uses that to generate proposals for the rest of the
>> functions.
>
>
> Good idea.


I would expect a broader study of fixes necessary for the library. We
should look at adding a std::ypoc as
the more intuitive spelling for std::reverse_copy, with the potential
intent to deprecate and remove the
completely non-intuitive status quo. Similarly, we should look at
completing the set of find-algorithms;
we have find_if, so we should probably also have find_else, find_for,
find_do and find_while, and potentially
also find_switch. In addition to that, if we have find_if_not, we
should probably also have find_if_and and
find_if_or.

--
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/CAFk2RUZYuvMj-Oi1toaRt7DoMsxzs%3DbbtfJA4j46Uk9O9_qAog%40mail.gmail.com.

.

On Fri, Apr 01, 2016 at 10:29:49AM +0300, Ville Voutilainen wrote:
> On 1 April 2016 at 10:20, Leo Heinsaar <leoheinsaar@gmail.com> wrote:
>
> I would expect a broader study of fixes necessary for the library. We
> should look at adding a std::ypoc as
> the more intuitive spelling for std::reverse_copy, with the potential
> intent to deprecate and remove the
> completely non-intuitive status quo. Similarly, we should look at
> completing the set of find-algorithms;
> we have find_if, so we should probably also have find_else, find_for,
> find_do and find_while, and potentially
> also find_switch. In addition to that, if we have find_if_not, we
> should probably also have find_if_and and
> find_if_or.

Maybe find_throw and find_goto as well?

On the other hand I think find_catch is sorely neeeded.

/MF

--
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/20160401074304.GA7221%40noemi.

.

------=_Part_4706_122434165.1459499159170
Content-Type: multipart/alternative;
 boundary="----=_Part_4707_1561449863.1459499159170"

------=_Part_4707_1561449863.1459499159170
Content-Type: text/plain; charset=UTF-8


>
> I would expect a broader study of fixes necessary for the library. We
> should look at adding a std::ypoc as
> the more intuitive spelling for std::reverse_copy, with the potential
> intent to deprecate and remove the
> completely non-intuitive status quo. Similarly, we should look at
> completing the set of find-algorithms;
> we have find_if, so we should probably also have find_else, find_for,
> find_do and find_while, and potentially
> also find_switch. In addition to that, if we have find_if_not, we
> should probably also have find_if_and and
> find_if_or.
>

Also a very useful bunch that totally deserves to be in the Standard.
For example, find_or_else(begin, end, std::terminate) could send a very
strong message to the program that it better find what I'm looking for.

--
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/dcc5f082-0164-4102-b539-6666b68df667%40isocpp.org.

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

<div dir=3D"ltr"><blockquote class=3D"gmail_quote" style=3D"margin: 0;margi=
n-left: 0.8ex;border-left: 1px #ccc solid;padding-left: 1ex;">I would expec=
t a broader study of fixes necessary for the library. We
<br>should look at adding a std::ypoc as
<br>the more intuitive spelling for std::reverse_copy, with the potential
<br>intent to deprecate and remove the
<br>completely non-intuitive status quo. Similarly, we should look at
<br>completing the set of find-algorithms;
<br>we have find_if, so we should probably also have find_else, find_for,
<br>find_do and find_while, and potentially
<br>also find_switch. In addition to that, if we have find_if_not, we
<br>should probably also have find_if_and and
<br>find_if_or.
<br></blockquote><div><br></div><div>Also a very useful bunch that totally =
deserves to be in the Standard.</div><div>For example, <font face=3D"courie=
r new, monospace">find_or_else(begin, end, std::terminate)</font> could sen=
d a very strong message to the program that it better find what I&#39;m loo=
king for.</div><div><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/dcc5f082-0164-4102-b539-6666b68df667%=
40isocpp.org?utm_medium=3Demail&utm_source=3Dfooter">https://groups.google.=
com/a/isocpp.org/d/msgid/std-proposals/dcc5f082-0164-4102-b539-6666b68df667=
%40isocpp.org</a>.<br />

------=_Part_4707_1561449863.1459499159170--
------=_Part_4706_122434165.1459499159170--

.

On sexta-feira, 1 de abril de 2016 10:29:49 PDT Ville Voutilainen wrote:
> We
> should look at adding a std::ypoc as
> the more intuitive spelling for std::reverse_copy

(and this is real)

There's a precedent. The /usr/bin/tac command does the inverse of /usr/bin/
cat.

--
Thiago Macieira - thiago (AT) macieira.info - thiago (AT) kde.org
   Software Architect - Intel Open Source Technology Center

--
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/1518944.hY73Fqdbvg%40tjmaciei-mobl4.

.

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

On 1 April 2016 at 01:30, Leo Heinsaar <leoheinsaar@gmail.com> wrote:

> I just noticed that the rest of the std::atoi(), std::itoa() and
>  std::iota() family is missing.
> I think we need to start an urgent work to be able to include those in
> C++17 to keep C++ relevant in the modern age.
> Was there any thought given to including the rest of the permutations at
> Jacksonville? I mean the following:
>
> std::aiot()
> std::aito()
> std::aoit()
> std::aoti()
> std::atio()
> std::iaot()
> std::iato()
> std::ioat()
> std::itao()
> std::oait()
> std::oati()
> std::oiat() =E2=80=93 This one will express a particularly painful part i=
n a
> program.
> std::oita()
> std::otai()
> std::otia()
> std::taio()
> std::taoi() =E2=80=93 Tactical Area Of Interest, obviously.
> std::tiao()
> std::tioa()
> std::toai() =E2=80=93 This will automatically convert your program into a=
n
> artificial intelligence engine that passes the Turing test.
> std::toia()
>

It doesn't seem very general.  Maybe we should extend next_permutation and
prev_permutation to generate the functions for us?
--=20
 Nevin ":-)" Liber  <mailto:nevin@eviloverlord.com>  +1-847-691-1404

--=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/CAGg_6%2BMO8NXZ7JUYM0k1hbq_DRdin%3Dz696WP%3D5QYn=
_BmvkMuMw%40mail.gmail.com.

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

<div dir=3D"ltr">On 1 April 2016 at 01:30, Leo Heinsaar <span dir=3D"ltr">&=
lt;<a href=3D"mailto:leoheinsaar@gmail.com" target=3D"_blank">leoheinsaar@g=
mail.com</a>&gt;</span> wrote:<br><div class=3D"gmail_extra"><div class=3D"=
gmail_quote"><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;b=
order-left:1px #ccc solid;padding-left:1ex"><div dir=3D"ltr">I just noticed=
 that the rest of the <font face=3D"courier new, monospace">std::atoi()</fo=
nt>,<font face=3D"courier new, monospace"> std::itoa()=C2=A0</font>and<font=
 face=3D"courier new, monospace">=C2=A0std::iota()</font> family is missing=
..<div>I think we need to start an urgent work to be able to include those i=
n C++17 to keep C++ relevant in the modern age.<div>Was there any thought g=
iven to including the rest of the permutations at Jacksonville? I mean the =
following:<br></div><div><br></div><div><div><font face=3D"courier new, mon=
ospace">std::aiot()</font></div><div><font face=3D"courier new, monospace">=
std::aito()</font></div><div><font face=3D"courier new, monospace">std::aoi=
t()</font></div><div><font face=3D"courier new, monospace">std::aoti()</fon=
t></div><div><font face=3D"courier new, monospace">std::atio()</font></div>=
<div><font face=3D"courier new, monospace">std::iaot()</font></div><div><fo=
nt face=3D"courier new, monospace">std::iato()</font></div><div><font face=
=3D"courier new, monospace">std::ioat()</font></div><div><font face=3D"cour=
ier new, monospace">std::itao()</font></div><div><font face=3D"courier new,=
 monospace">std::oait()</font></div><div><font face=3D"courier new, monospa=
ce">std::oati()</font></div><div><font face=3D"courier new, monospace">std:=
:oiat()</font><span style=3D"font-family:arial,sans-serif">=C2=A0=E2=80=93<=
/span><span style=3D"font-family:arial,sans-serif">=C2=A0This one will expr=
ess a particularly painful part in a program.</span></div><div><font face=
=3D"courier new, monospace">std::oita()</font></div><div><font face=3D"cour=
ier new, monospace">std::otai()</font></div><div><font face=3D"courier new,=
 monospace">std::otia()</font></div><div><font face=3D"courier new, monospa=
ce">std::taio()</font></div><div><font face=3D"courier new, monospace">std:=
:taoi()</font><span style=3D"font-family:arial,sans-serif">=C2=A0=E2=80=93<=
/span><span style=3D"font-family:arial,sans-serif">=C2=A0Tactical Area Of I=
nterest, obviously.</span></div><div><font face=3D"courier new, monospace">=
std::tiao()</font></div><div><font face=3D"courier new, monospace">std::tio=
a()</font></div><div><font face=3D"courier new, monospace">std::toai()</fon=
t><font face=3D"arial, sans-serif">=C2=A0=E2=80=93=C2=A0This will automatic=
ally convert your program into an artificial intelligence engine that passe=
s the Turing test.</font></div><div><font face=3D"courier new, monospace">s=
td::toia()</font></div></div></div></div></blockquote><div><br></div><div>I=
t doesn&#39;t seem very general.=C2=A0 Maybe we should extend next_permutat=
ion and prev_permutation to generate the functions for us?</div></div>-- <b=
r><div class=3D"gmail_signature"><div dir=3D"ltr"><div><div dir=3D"ltr"><di=
v>=C2=A0Nevin &quot;:-)&quot; Liber=C2=A0 &lt;mailto:<a href=3D"mailto:nevi=
n@eviloverlord.com" target=3D"_blank">nevin@eviloverlord.com</a>&gt; =C2=A0=
+1-847-691-1404</div></div></div></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/CAGg_6%2BMO8NXZ7JUYM0k1hbq_DRdin%3Dz6=
96WP%3D5QYn_BmvkMuMw%40mail.gmail.com?utm_medium=3Demail&utm_source=3Dfoote=
r">https://groups.google.com/a/isocpp.org/d/msgid/std-proposals/CAGg_6%2BMO=
8NXZ7JUYM0k1hbq_DRdin%3Dz696WP%3D5QYn_BmvkMuMw%40mail.gmail.com</a>.<br />

--089e0122e720683870052f70b5c1--

.