Re: Legit Warnings or not

["Dmitry A. Kazakov" <mailbox@dmitry-kazakov.de>]

On Tue, 2 Aug 2011 16:30:24 -0500, Randy Brukardt wrote:

> Either you are allowing changing the object to anything in the class, 
> or you are not allowing it to be changed at all. No middle ground there.

When I declare

   type A is array (...) of S'Class;

1. Are all elements constrained to same specific type?

2. May object types change after being initialized?

3. Which rules apply to view conversions, e.g. T'Class (A (10)). Could it
be then assigned to which types, same, others?

4. In which relation are slices of the array and arrays of T'Class when T
is related to S? [Classes of arrays vs. arrays of classes vs. classes of
arrays of classes etc.]

5. I am horrified what kind of "accessibility rules" might get invented for
passing elements of this "array" here and there.

[The behavior of types upon composition is a very non-trivial issue.]

> And there is no "control over copying". These are normal "parts" of the 
> object, and they're always copied. If you don't want copying, then you need 
> to use some sort of reference (cursor or access type). (Of course, an 
> implementation can always do an "as-if" implementation, but the model is 
> always deep copying.)

Which would make the compiler implementation unusable in so many cases.

-- 
Regards,
Dmitry A. Kazakov
http://www.dmitry-kazakov.de