October 2013 - Boost - lists.preview.boost.org

Review request: Require compiler support for partial template specialization.
by Stephen Kelly 01 Oct '13

01 Oct '13

Hi there, Following from http://thread.gmane.org/gmane.comp.lib.boost.devel/243923/focus=243924 I am posting a more focused and specific request to review a patch to bump compiler requirements to require support for partial template specialization. This allows the removal of a lot of workaround code: src/boost-trunk{master}$ ../kf5/remove_def.py BOOST_NO_TEMPLATE_PARTIAL_SPECIALIZATION src/boost-trunk{master}$ git diff --shortstat 192 files changed, 4798 deletions(-) Obviously I would not commit all of that as a single patch. Any comments? Thanks, Steve.

4 8

Do/can we have a C++11 variadic integer list?
by Daryle Walker 01 Oct '13

01 Oct '13

I'm talking about this: template < std::size_t ...N > struct indices_too { using next = indices_too<N..., sizeof...(N)>; }; template < std::size_t N > struct make_indices_too { using type = typename make_indices_too<N - 1u>::type::next; }; template < > struct make_indices_too<0u> { using type = indices_too<>; }; I've written things like this 4 times for my prototype Boost classes, and I want it in Boost already so I can just reference that version. Something like it will come in C++14, but we could provide it here for C++11 users? Do we already have one? Here's how to use one: template < typename Function, typename T, class Tuple, std::size_t ...I > void apply_x_and_exploded_tuple_impl( Function &&f, T &&x, Tuple &&t, indices_too<I...> ) { using std::forward; forward<Function>( f )( forward<T>(x), forward<typename std::tuple_element<I, typename std::remove_reference<Tuple>::type>::type>(std::get<I>( t ))... ); } template < typename Function, typename T, class Tuple > void apply_x_and_exploded_tuple( Function &&f, T &&x, Tuple &&t ) { using std::forward; apply_x_and_exploded_tuple_impl( forward<Function>(f), forward<T>(x), forward<Tuple>(t), typename make_indices_too<std::tuple_size<typename std::remove_reference<Tuple>::type>::value>::type{} ); } Daryle W.

3 2

orphaned tickets
by Joel Falcou 01 Oct '13

01 Oct '13

What's the protocol to handle lingering tickets of un maintained components. I wish #9169 and #9170 could be merged to trunk soonish. I cna do it myself but i dont want to breach any protocol. Regards

3 2