Topic: Deadline for Library Fundamentals TS
Author: =?UTF-8?Q?Andrzej_Krzemie=C5=84ski?= <akrzemi1@gmail.com>
Date: Fri, 21 Feb 2014 12:35:31 -0800 (PST)
Raw View
------=_Part_329_19827751.1393014931420
Content-Type: text/plain; charset=UTF-8
Hi Everyone,
I wanted to ask about the procedures and/or deadlines regarding Library
Fundamentals TS. Is there yet any time to propose some fixes to one of the
accepted libraries, before the final version is emitted? I just realized
Optional is missing some fairly obvious function overloads. Do I have any
chance adding them to Library Fundamentals TS, or do I have to wait till
next year?
Regards,
&rzej
--
---
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.
Visit this group at http://groups.google.com/a/isocpp.org/group/std-proposals/.
------=_Part_329_19827751.1393014931420
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
<div dir=3D"ltr">Hi Everyone,<br>I wanted to ask about the procedures and/o=
r deadlines regarding Library Fundamentals TS. Is there yet any time to pro=
pose some fixes to one of the accepted libraries, before the final version =
is emitted? I just realized Optional is missing some fairly obvious functio=
n overloads. Do I have any chance adding them to Library Fundamentals TS, o=
r do I have to wait till next year?<br><br>Regards,<br>&rzej<br></div>
<p></p>
-- <br />
<br />
--- <br />
You received this message because you are subscribed to the Google Groups &=
quot;ISO C++ Standard - Future Proposals" group.<br />
To unsubscribe from this group and stop receiving emails from it, send an e=
mail to std-proposals+unsubscribe@isocpp.org.<br />
To post to this group, send email to std-proposals@isocpp.org.<br />
Visit this group at <a href=3D"http://groups.google.com/a/isocpp.org/group/=
std-proposals/">http://groups.google.com/a/isocpp.org/group/std-proposals/<=
/a>.<br />
------=_Part_329_19827751.1393014931420--
.
Author: Ville Voutilainen <ville.voutilainen@gmail.com>
Date: Fri, 21 Feb 2014 22:57:46 +0200
Raw View
On 21 February 2014 22:35, Andrzej Krzemie=C5=84ski <akrzemi1@gmail.com> wr=
ote:
> Hi Everyone,
> I wanted to ask about the procedures and/or deadlines regarding Library
> Fundamentals TS. Is there yet any time to propose some fixes to one of th=
e
> accepted libraries, before the final version is emitted? I just realized
> Optional is missing some fairly obvious function overloads. Do I have any
> chance adding them to Library Fundamentals TS, or do I have to wait till
> next year?
I am under the impression that the Fundamentals TS is planned to
come out of Rapperswil (for a PDTS ballot), so there's still time to
include fixes to
optional. And there's time after that ballot, too, if national bodies reque=
st
fixes.
--=20
---=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.
Visit this group at http://groups.google.com/a/isocpp.org/group/std-proposa=
ls/.
.
Author: Jeffrey Yasskin <jyasskin@google.com>
Date: Fri, 21 Feb 2014 13:03:28 -0800
Raw View
There's definitely time for bugfixes to anything in the TS. New
features will get delayed to v2. The exact division between the two
will have to be discussed on a case-by-case basis.
On Fri, Feb 21, 2014 at 12:35 PM, Andrzej Krzemie=C5=84ski
<akrzemi1@gmail.com> wrote:
> Hi Everyone,
> I wanted to ask about the procedures and/or deadlines regarding Library
> Fundamentals TS. Is there yet any time to propose some fixes to one of th=
e
> accepted libraries, before the final version is emitted? I just realized
> Optional is missing some fairly obvious function overloads. Do I have any
> chance adding them to Library Fundamentals TS, or do I have to wait till
> next year?
>
> Regards,
> &rzej
>
> --
>
> ---
> 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.
> Visit this group at
> http://groups.google.com/a/isocpp.org/group/std-proposals/.
--=20
---=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.
Visit this group at http://groups.google.com/a/isocpp.org/group/std-proposa=
ls/.
.
Author: Andrzej Krzemienski <akrzemi1@gmail.com>
Date: Fri, 21 Feb 2014 22:38:32 +0100
Raw View
--089e01227f4488907e04f2f1714f
Content-Type: text/plain; charset=ISO-8859-1
2014-02-21 22:03 GMT+01:00 Jeffrey Yasskin <jyasskin@google.com>:
> There's definitely time for bugfixes to anything in the TS. New
> features will get delayed to v2. The exact division between the two
> will have to be discussed on a case-by-case basis.
>
So, can you give me a hint here? I would like to add rvalue reference
overloads for member functions value(), operator* and operator->. Similarly
to what member function value_or() already provides.
1. Would that qualify for a bug fix or a feature?
2. Does it need a separate paper, or a defect report would suffice?
Regards,
&rzej
--
---
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.
Visit this group at http://groups.google.com/a/isocpp.org/group/std-proposals/.
--089e01227f4488907e04f2f1714f
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
<div dir=3D"ltr"><br><div class=3D"gmail_extra"><div class=3D"gmail_quote">=
2014-02-21 22:03 GMT+01:00 Jeffrey Yasskin <span dir=3D"ltr"><<a href=3D=
"mailto:jyasskin@google.com" target=3D"_blank">jyasskin@google.com</a>><=
/span>:<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex">There's definitely time for bugfixes to =
anything in the TS. New<br>
features will get delayed to v2. The exact division between the two<br>
will have to be discussed on a case-by-case basis.<br></blockquote><div><br=
></div><div>So, can you give me a hint here? I would like to add rvalue ref=
erence overloads for member functions value(), operator* and operator->.=
Similarly to what member function value_or() already provides.<br>
</div><div>1. Would that qualify for a bug fix or a feature?<br></div><div>=
2. Does it need a separate paper, or a defect report would suffice?<br><br>=
</div><div>Regards,<br></div><div>&rzej<br></div></div></div></div>
<p></p>
-- <br />
<br />
--- <br />
You received this message because you are subscribed to the Google Groups &=
quot;ISO C++ Standard - Future Proposals" group.<br />
To unsubscribe from this group and stop receiving emails from it, send an e=
mail to std-proposals+unsubscribe@isocpp.org.<br />
To post to this group, send email to std-proposals@isocpp.org.<br />
Visit this group at <a href=3D"http://groups.google.com/a/isocpp.org/group/=
std-proposals/">http://groups.google.com/a/isocpp.org/group/std-proposals/<=
/a>.<br />
--089e01227f4488907e04f2f1714f--
.
Author: Jeffrey Yasskin <jyasskin@google.com>
Date: Fri, 21 Feb 2014 13:41:50 -0800
Raw View
On Fri, Feb 21, 2014 at 1:38 PM, Andrzej Krzemienski <akrzemi1@gmail.com> wrote:
>
> 2014-02-21 22:03 GMT+01:00 Jeffrey Yasskin <jyasskin@google.com>:
>
>> There's definitely time for bugfixes to anything in the TS. New
>> features will get delayed to v2. The exact division between the two
>> will have to be discussed on a case-by-case basis.
>
>
> So, can you give me a hint here? I would like to add rvalue reference
> overloads for member functions value(), operator* and operator->. Similarly
> to what member function value_or() already provides.
> 1. Would that qualify for a bug fix or a feature?
I don't know. It's self-contained enough that I wouldn't object to
taking it for v1, if we decide to take it at all.
> 2. Does it need a separate paper, or a defect report would suffice?
A defect report would suffice to get us to talk about it, but it would
probably be good to write a paper to explore why it's useful and what
corner cases it introduces.
--
---
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.
Visit this group at http://groups.google.com/a/isocpp.org/group/std-proposals/.
.