Fix array literal slices with range operators #142
Merged
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.
Problem
Array literal slices containing range operators like ('a','b','c','d','e','f')[0..5] were returning only the first element instead of the full slice.
Root Cause
The handleArrowArrayDeref method was using single-element optimization for all single-element array literal indices, but range operators need to be evaluated in LIST context to expand to multiple indices.
Solution
Changes
Test Results
Trade-offs
Expression slices like (@foo,@bar)[0..5] are not fixed by this change to avoid breaking hash.t functionality. Those would require a separate, more careful approach.