[class.base.init] p9

In a non-delegating constructor, if a given potentially constructed subobject is not designated by a mem-initializer-id (including the case where there is no mem-initializer-list because the constructor has no ctor-initializer), then

The rules that are defined by [class.base.init] p9 intend to cover all cases about initialization associated with a non-delegating constructor.

[class.copy.ctor#note-7]

[Note 7: Default member initializers of non-static data members are ignored. See also the example in [class.base.init]. — end note]

The above note wants to expound implicitly defined copy/move constructor suppresses the application of [class.base.init] p9, however, it is just a note instead of a normative rule. Furthermore, I cannot find the example in [class.base.init]. Should we give a normative rule for [class.base.init] p9, which will exclude applying to the implicitly defined copy/move constructor?

In a non-delegating constructor that is not an implicitly defined copy/move constructor, if a given potentially constructed subobject is not designated by a mem-initializer-id (including the case where there is no mem-initializer-list because the constructor has no ctor-initializer), then