On 14 Nov., 01:38, Scott Meyers <use...@aristeia.com> wrote:
> My understanding is that the following changes were agreed upon in the last
> standardization meeting:
> - std::thread's variadic constructor is to be retained.

This is true as written, but the state of affairs is still
volatile ;-):

http://www.open-std.org/jtc1/sc22/wg21/docs/lwg-active.html#1176

> - std::async taking variadic arguments is to be added.

Yes.

> - std::unique_future was renamed std::future.

Yes.

> - is_ready, has_value, and has_exception were removed from the futures APIs.

Yes.

> - std::atomic_future was added.

Yes.

> - register is deprecated as a storage class specifier.  (Presumably it will
>     remain a keyword.)

Yes, and the latter comment is true as well.

HTH & Greetings from Bremen,

Daniel Kr   gler


--
[ comp.std.c++ is moderated.  To submit articles, try just posting with ]
[ your news-reader.  If that fails, use mailto:std-c++@netlab.cs.rpi.edu]
[              --- Please see the FAQ before posting. ---               ]
[ FAQ: http://www.comeaucomputing.com/csc/faq.html                      ]

On Nov 13, 7:38 pm, Scott Meyers <use...@aristeia.com> wrote:
> My understanding is that the following changes were agreed upon in the last
> standardization meeting:
> - std::thread's variadic constructor is to be retained.

This has not been decided.  Here are the relevant issues:

http://www.open-std.org/jtc1/sc22/wg21/docs/lwg-active.html#929
http://www.open-std.org/jtc1/sc22/wg21/docs/lwg-active.html#1176

In Santa Cruz we decided that we were not going to make a decision in
Santa Cruz, but that we wanted to be ready to go either way.  LWG 929
is getting wording ready to keep it variadic.  LWG 1176 is for the
purpose of removing it.  Neither issue is closed.

-Howard


--
[ comp.std.c++ is moderated.  To submit articles, try just posting with ]
[ your news-reader.  If that fails, use mailto:std-c++@netlab.cs.rpi.edu]
[              --- Please see the FAQ before posting. ---               ]
[ FAQ: http://www.comeaucomputing.com/csc/faq.html                      ]

My understanding is that the following changes were agreed upon in the last
standardization meeting:
- std::thread's variadic constructor is to be retained.
- std::async taking variadic arguments is to be added.
- std::unique_future was renamed std::future.
- is_ready, has_value, and has_exception were removed from the futures APIs.
- std::atomic_future was added.
- register is deprecated as a storage class specifier.  (Presumably it will
    remain a keyword.)

I would appreciate it if somebody would confirm that these are correct (or let
me know how they are wrong if not).

Thanks,

Scott

--
[ comp.std.c++ is moderated.  To submit articles, try just posting with ]
[ your news-reader.  If that fails, use mailto:std-c++@netlab.cs.rpi.edu]
[              --- Please see the FAQ before posting. ---               ]
[ FAQ: http://www.comeaucomputing.com/csc/faq.html                      ]

Scott Meyers wrote:
>
> My understanding is that the following changes were agreed upon in the last
> standardization meeting:
> - std::thread's variadic constructor is to be retained.
> - std::async taking variadic arguments is to be added.
> - std::unique_future was renamed std::future.
> - is_ready, has_value, and has_exception were removed from the futures APIs.
> - std::atomic_future was added.
> - register is deprecated as a storage class specifier.  (Presumably it will
>   remain a keyword.)
>
> I would appreciate it if somebody would confirm that these are correct (or let
> me know how they are wrong if not).
>

The answers to all these questions and more are in the post-meeting mailing.

--
 Pete
Roundhouse Consulting, Ltd. (www.versatilecoding.com) Author of
"The Standard C++ Library Extensions: a Tutorial and Reference"
(www.petebecker.com/tr1book)

[ comp.std.c++ is moderated.  To submit articles, try just posting with ]
[ your news-reader.  If that fails, use mailto:std-c++@netlab.cs.rpi.edu]
[              --- Please see the FAQ before posting. ---               ]
[ FAQ: http://www.comeaucomputing.com/csc/faq.html                      ]