AggregateError.prototype.toString

[bakkot]

From #33:

AggregateError.prototype.toString: should this exist and do something different than Error.prototype.toString?

I think it would be useful to have it report messages from the underlying errors, though I'm not sure exactly what that ought to look like. It could at least report the number of errors it is wrapping, failing that.

cc @ljharb

[ljharb]

I would hope it toStrings each item of the array so as to maximize usefulness in debugging, but a count of errors would be a good minimum.

[chicoxyzzy]

This has been implemented in #37 with number of errors. PTAL at commit: 44b1c52

[ljharb]

@mathiasbynens at this point, it seems that AggregateError.prototype.toString is identical to Error.prototype.toString - should they be ===? Or, should there be something about errors mentioned in AggregateError.prototype.toString?

[devsnek]

Error#toString and AggregateError#toString are identical except for the default name value (Error vs AggregateError). For consistency, it would probably be best to only have Error#toString, and then an internal slot or something could override the default name value.

[devsnek]

Actually thinking about this more, I don't think there is even a need for overriding the default. AggregateError#toString should probably just be removed.