I hope I'm wrong, but I don't think this proposal would allow us to solve [URL] according to the mentioned caveat.

This is because if my own code set `Validators.required` in a form control, then `@angular/material` has no way to know which function reference to use to check for the required validator presence. Is this correct ?

I was under the impression that this use-case was one of the major thing to solve.

If associating a validator with a name would properly solve all use-cases, maybe a redesign of the Forms API, that also include all the good things from #31963, should be considered, instead of doing half-measures ? A sort of `ReactiveFormsV2Module` ?