Boost C++ Libraries: Ticket #5816: any_range requires copyable elements

voivoid@… — Fri, 18 Oct 2013 13:57:20 GMT

This problem also prevents a use of abstract class pointers. Any chances this is going to be fixed?

I wonder if the problem could be solved with something like this:

any_iterator_interface.hpp
49,51c49,53
<             typedef typename remove_const<
<                 typename remove_reference<Reference>::type
<             >::type reference_as_value_type;
---
>             typedef typename mpl::if_<
>                 is_trivially_copy_constructible<typename remove_reference<Reference>::type>
>               , typename remove_const<typename remove_reference<Reference>::type>::type
>               , Reference
>             >::type reference_as_value_type;

anonymous — Tue, 04 Feb 2014 07:52:00 GMT

I also encountered this problem recently. It prevents me from using boost::any_range as an object interface abstraction, since i don't want the values copied (i want to expose iterators to Base, and supply a container of Derived objects in the implementation).

I do not see any good reason to require copying when all any_range is is an abstract view into the source range. That elements aren't going to be copied should be made into a guarantee.

This is a 2 year old bug, is it possible that it can be fixed soon?

status changed

Neil Groves — Fri, 21 Feb 2014 20:28:11 GMT

status new → assigned

Yes it will be fixed soon. I've got a bunch more time than I have and I'm trying hard to catch up.

status changed; resolution set

Neil Groves — Sun, 02 Mar 2014 23:03:43 GMT

status assigned → closed
resolution → fixed