Why does a range need a copy (instead of a move) constructor?

Why does a range need a copy (instead of a move) constructor?

TBB's range concept requires a copy constructor. Unfortunately, the reference manual does not specify why this is required, and algorithmically duplicating a range makes no/little sense. I can see that moving a range around between different parts of the algorithms may be necessary, but this can be achieved either by copying pointers or by using the move constructor. Are there plans to relax the concept to allow move-only constructible ranges (but still work with copy-constructible)? Or are there reasons (which) why this cannot be done?

2 posts / 0 new
Last post
For more complete information about compiler optimizations, see our Optimization Notice.

A Range is just a pair of numbers/pointers/iterators: any referents are stored elsewhere.

Leave a Comment

Please sign in to add a comment. Not a member? Join today