Re: [boost] [Range] Range adaptor approach for temporary range lifetime issue

on Sun Jun 17 2012, Michel Morin <mimomorin-AT-gmail.com> wrote:

Side note:

* There is also a fully automatic approach (i.e. when an rvalue range is adapted, `moved_range` is automatically used without piping it to `moved` adaptor). But this approach incurs unnecessary overhead when passing them to functions, because function arguments do not have the lifetime issue and we don't need to use `moved_range`. So I prefer the "manual" approach.

Could you illustrate this with an example? I'd like to understand the trade-off you're making. Thanks, -- Dave Abrahams BoostPro Computing http://www.boostpro.com