10 May
2010
10 May
'10
1:24 p.m.
Neil Groves wrote:
This can't easily be remedied since the Range Concept is non-copyable, and we obviously can't pass a const reference as the target to the fill algorithm. Making the Range Concept cheaply copyable would mean that the standard containers were no longer a model of the Range Concepts. I am currently investigating extending the sub_range
It should be perfectly ok to make iterator_range and sub_range cheaply copyable, since they just wrap iterators. No need to extend the range concepts for that; iterator_range would simply provide more than those concepts.