Re: [boost] A design for geometric objects

Also, geometry objects can be arbitrarily heavy. One polygon has the

Simonson, Lucanus J wrote: potential to be many megabytes in my application domain.

While it is possible to return by value for light objects and pass outputs as arguments for heavy objects, it would make for a highly inconsistent and unintuitive API.

For clarification, by light objects I mean proxies and adaptors, in a DSEL kind of way. Basically the aim is that the algorithm is not applied when you call the function, but when you copy the result. The spirit is fairly similar to the range adaptors of Boost.RangeEx for example.