Ruling out arbitrary cost copy construction?

[Bruno Medeiros]

On 06/10/2010 17:34, Andrei Alexandrescu wrote:
>
>
> or similar. However, a sealed range does not offer references, so trying
> e.g.
>
> swap(r1.front, r2.front);
>
> will not work. This is a problem.

Why doesn't a sealed range offer references? Is it to prevent modifying 
the elements being iterated?
(I searched google and TDPL but couldn't find any info on sealed ranges)

-- 
Bruno Medeiros - Software Engineer