Subject: Re: [boost] [type_erasure] Review started (July 18-27, 2012)
From: Paul A. Bristow (pbristow_at_[hidden])
Date: 2012-08-02 09:41:27
> -----Original Message-----
> From: boost-bounces_at_[hidden] [mailto:boost-bounces_at_[hidden]] On Behalf Of Steven
> Sent: Friday, July 27, 2012 9:19 PM
> To: boost_at_[hidden]
> Subject: Re: [boost] [type_erasure] Review started (July 18-27, 2012)
> The main benefit for this is for type
> erased function arguments:
> typedef mpl::vector<
> same_type<random_access_iterator<_iter>::value_type, _a>,
> callable<bool(const _a&, const _a&), _f>,
> > sort_requirements;
> void sort_impl(iter_type, iter_type, func_type);
> // capture the arguments and forward to the // separately compiled implementation template<class
> class F> void sort(Iter, Iter, F);
In trying to work up this example, I couldn't find move_constructible and move_assignable - are this
But should work without this?
This also highlighted the usefulness of an index - I tried to build one using b2 --enable-index ,
but the simple hooks and eyes are missing.
There are quite lot of possible requirements, and they each have their include file.
> Requirements like this are very common
> in generic programming.
> > The good point is that the reference documentation looks complete and helpful.
> In Christ,
> Steven Watanabe
> Unsubscribe & other changes: http://lists.boost.org/mailman/listinfo.cgi/boost
Boost list run by bdawes at acm.org, gregod at cs.rpi.edu, cpdaniel at pacbell.net, john at johnmaddock.co.uk