20 Jul
2011
20 Jul
'11
4:05 a.m.
Updating the transformed_range constructor to take a template argument, as I showed, works perfectly, and is simpler than anything else.
This only works if the other range type happens to have the same iterator type. IMO this is a rare situation - most range types have their own iterator types.
That's why I suggest that this be applied to the Boost code. Is there a way for a mere user to submit that formally?
You can open a new ticket in the Boost Issue Tracker [1], and attach a patch implementing this. Regards, Nate. [1] https://svn.boost.org/trac/boost