New Issue: Error Message: Should operator method calls look the same as standalone operator calls?

17539, "lydia-duncan", "Error Message: Should operator method calls look the same as standalone operator calls?", "2021-04-07T17:47:08Z"

Today if a call fails and reports the call stack involving an operator method, we'll report it as, e.g.:

foo.chpl:n: called as MyRecord.=(lhs: MyRecord(0), rhs: MyRecord(0))

Vass points out that we can't explicitly write a call like that today. Should we modify the message when the function called is an operator method so that it doesn't include the type prefix? E.g.

foo.chpl:n: called as =(lhs: MyRecord(0), rhs: MyRecord(0))