RFC: naming for FrontTransversal and Transversal ranges
Rainer Deyke
rainerd at eldwood.com
Sat May 2 00:39:27 PDT 2009
Robert Jacques wrote:
> On Fri, 01 May 2009 15:37:56 -0400, Rainer Deyke <rainerd at eldwood.com>
> wrote:
>> All containers need to support copying.
>
> No they don't.
There is no conceptual problem with a non-copyable struct. However, in
order to be a considered a container, the struct must at least support
read-only iteration over its contents. If iteration is possible, then
so is copying.
You can have non-copyable value types, but they can't be containers.
--
Rainer Deyke - rainerd at eldwood.com
More information about the Digitalmars-d
mailing list