Emit explanatory error message for iteration on CartesianIndex #24284
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.
As suggested in #23982. Sometimes these messages are helpful, but they can occasionally cause problems. In this case the most confusing part of the message would be if someone hit this in the context of
and the user might wonder what splatting has to do with it. Nevertheless I suspect that splatting is how most people hit this issue.
But I am not attached to this. I've also deliberately not added a test for this behavior, since once the length can be inferred we will want to support iteration over the elements of
CartesianIndex
.