This page is a snapshot from the LWG issues list, see the Library Active Issues List for more information and the meaning of C++14 status.
Section: 220.127.116.11 [tuple.creation] Status: C++14 Submitter: Marshall Clow Opened: 2013-07-30 Last modified: 2017-09-10
Priority: Not Prioritized
View other active issues in [tuple.creation].
View all other issues in [tuple.creation].
View all issues with C++14 status.
Addresses ES 11
In n3471, a bunch of routines from header <tuple> were made constexpr.make_tuple/tuple_cat/get<>(tuple)/relational operators — all these were "constexpr-ified". But not forward_as_tuple. Why not? This was discussed in Portland, and STL opined that this was "an omission" (along with tuple_cat, which was added) In discussion on firstname.lastname@example.org list, Pablo agreed that forward_as_tuple should be constexpr.
Moved to Immediate, this directly addresses an NB comment and the wording is non-controversial.
Accept for Working Paper
This wording is relative to N3691.
Change header <tuple> synopsis, 19.5.1 [tuple.general] as indicated:
template <class... Types> tuple<Types&&...> forward_as_tuple(Types&&...) noexcept;
Change 18.104.22.168 [tuple.creation] before p5 as indicated:
template <class... Types> tuple<Types&&...> forward_as_tuple(Types&&... t) noexcept;