!comment This file contains Corrigendum conflicts for the first Corrigendum
!comment for Ada 2022. Conflicts occur when multiple issues change the same
!comment paragraph of the standard.
!comment This file (and the reading of it in the program) would need to
!comment be changed for a new Corrigendum or Amendment.
!comment The paragraphs must be in sorted order!!

!comment None yet. The below shows a sample conflict.
!comment !corrigendum 3.2.4(4/3)
!comment !AI-0071-1
!comment !AI-0099-1

!comment @drepl
!comment @xbullet<For a (first) subtype defined by a derived type declaration,
!comment the predicates of the parent subtype and the progenitor subtypes apply.>
!comment @dby
!comment @xbullet<For a (first) subtype defined by a type declaration, any
!comment predicates of parent or progenitor subtypes apply.>

!corrigendum 4.3.5(11/5)
!AI-0021-1
!AI-0032-1

@drepl
For an Aggregate aspect, the key type of Assign_Indexed shall be the same 
type as that of the parameters of New_Indexed. Additionally, if both 
Add_Unnamed and Assign_Indexed are specified, the final parameters shall 
be of the same type @emdash the element type of the container type.
@dby
For an Aggregate aspect, neither the element type nor the key type (if any) 
of the container type shall be a limited type. Additionally, the key type of
Assign_Indexed shall be the same type as that
of the parameters of New_Indexed and that type shall be a discrete type. If
both Add_Unnamed and Assign_Indexed are specified, the final parameters shall
be of the same type @emdash the element type of the container type.

None of the subprograms specified for an Aggregate aspect shall have a formal 
access parameter, nor an explicitly aliased formal parameter.

If the container type @i<T> is not abstract, then none of the subprograms 
specified in the Aggregate aspect for @i<T> shall be abstract.

In addition to the places where Legality Rules normally apply (see 12.3),
these rules apply also in the private part of an instance of a generic unit.