Remove repetitive wording.

[amartini51]

Fixes rdar://59618453

[amartini51]

@gottesmm I'm not 100% sure of the last piece of this change — do you use ManagedBufferPointer in addition to, or instead of ManagedBuffer when multiple classes are being used for storage?

[gottesmm]

@amartini51 I am not the person to review this change. I would ask one of the stdlib folks. I think that @lorentey would be a good one.

[lorentey]

👍

[lorentey]

@swift-ci smoke test

[amartini51]

@gottesmm Thanks. Looks like I can't remove you as a reviewer, but you can "dismiss" the request to review.

@lorentey I'm not 100% sure of the last piece of this change — do you use ManagedBufferPointer in addition to, or instead of ManagedBuffer when multiple classes are being used for storage?

[lorentey]

Ah -- ManagedBufferPointer does support wrapping classes that aren't ManagedBuffer subclasses, although this isn't exercised very often. (The big limitation is that such a class must have no stored properties.)

(One use case for this is having all empty instances of a generic container type use the same type-punned empty singleton storage, no matter what the Element type is.)

[CodaFi]

@swift-ci smoke test Linux platform