19779, "mppf", "should class assignment overload be checked more thoroughly?", "2022-05-10T13:16:07Z"
PR #19306 updates test/classes/assignments/noAssignClass.good to remove a couple of cases that previously resulted in an error. The reason is that the visibility changes meant that some = overloads from the test were not resolved at all. That brought up the question in my mind - should the Can't overload assignments for class types error be issued even for an assignment that is not called?
In earlier versions of PR #19306, I looked at raising this error if there is a candidate function for = on classes, even if that function is not selected as the best candidate. However, that lead to duplicate errors.
Should we do something to improve the situation, and if so, what?