Re: Assignment access type with discriminants

["G.B." <bauhaus@notmyhomepage.invalid>]

On 22.03.23 10:19, Dmitry A. Kazakov wrote:
> I stumbled on a curious fact.
> 
> The value of an object with a discriminant can be changed to a value with a different discriminant if the type's discriminants are defaulted.
> 
> Right?
> 
> Wrong! Not through an access type!
> 
> procedure Test is
>     type F is (F1, F2, F3);
>     type Foo (K : F := F1) is record
>        case K is
>           when F1 =>
>              X1 : Integer;
>           when F2 =>
>              X2 : Float;
>           when F3 =>
>              X3 : String (1..2);
>        end case;
>     end record;
>     type Foo_Ptr is access all Foo;
>     X : aliased Foo;
>     P : Foo_Ptr := X'Access;
> begin
>     X := (F2, 1.0);   -- OK
>     P.all := (F1, 3); -- Error!
> end Test;

Some experiments point at the general access type.

    type Foo_Ptr is access Foo; -- sans `all`
    X : Foo;
    P : Foo_Ptr := new Foo;
    type Foo1 is new Foo_Ptr (K => F1);
begin
    X := (F2, 1.0);   -- OK
    P.all := (F1, 3); -- _no_ Error!
    Foo1 (P).all := (F1, 3);
end Test;

(Doesn't rejection for general access types seem reasonable
if assignment would otherwise require adjusting the storage
layout of a variable, including all access paths to components?
Just guessing.)