Always use summary for BoundsError, even with non-AbstractArrays #32058
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Previously, BoundsError used
showwhen the container wasn't an AbstractArray. That could print a lot of stuff, and customizing it required changing the behaviour ofshow. Now it always usessummary, so users can define their ownsummaryto customize the display here.Also
summaryof a tuple now displays the whole tuple instead of its type. That's usually shorter than printing the type, and it keeps the existing behaviour for BoundsError.