19697, "vasslitvinov", "TaskErrors to use an intuitive ordering for its message()", "2022-04-22T16:10:33Z"
This issue requests a modification in how a TaskErrors builds its message().
Background: TaskErrors uses an ordering among the errors it contains to determine the first and the last error to show in its message(). Currently the ordering is based on message() of individual errors.
This requests is for the ordering to be based on chpl_describe_error() of the individual errors. Rationale: those are the strings reflected in TaskErrors.message(). For example, consider a TaskErrors that contains three errors: Error1, Error2, Error1, in this order, each with an empty message(). Currently TaskErrors.message() contains Error1: ... Error1:. Instead, it makes more sense if it contained Error1: ... Error2:. This approach is also more intuitive when the individual messages are not empty.
Test:
test/errhandling/parallel/taskerrors-write.chpl