Introduce a new attribute `step` in Range
As described in #13904, Numo::NArray and PyCall touches internal structure of Enumerator to obtain the argument of
This information is necessary to realize the same manner of the utilization of Python's slices.
In this ticket, I propose to introduce the new attribute
step in an instance of
Its role is same as the
step attribute of Python's slice.
Range#step should be changed to return a new Range object with the given step value instead of an Enumerator.
The default value of
step attribute is
nil, and it means that step is 1.
Updated by Eregon (Benoit Daloze) over 1 year ago
That's a big breaking change, and Range then needs to know about something like a "step value" which makes it more complex.
Why not introducing your own StepRange or so in PyCall then?
BTW, I think #13904 is more reasonable,
and only makes information that is always needed anyway and already can be observed though Enumerator#inspect available for other uses.
e.g. if someone wants to pretty-print an Enumerator differently than #inspect, they should be able to get the receiver, method and arguments, no point to hide that, it's already user-visible in #inspect.
Updated by mrkn (Kenta Murata) over 1 year ago
I want this feature for specifying a sliced view of a multi-dimensional array.
In Python, it can be represented by using slice notation or a slice object:
>>> ary = numpy.arange(0, 36).reshape((6, 6)) >>> ary array([[ 0, 1, 2, 3, 4, 5], [ 6, 7, 8, 9, 10, 11], [12, 13, 14, 15, 16, 17], [18, 19, 20, 21, 22, 23], [24, 25, 26, 27, 28, 29], [30, 31, 32, 33, 34, 35]]) >>> ary[1:5:2, slice(1, 5, 2)] array([[ 7, 9], [19, 21]])
In the above example,
1:5:2 is a slice notation, and
slice(1, 5, 2) is a slice object.
Both have the same mean: from 1 to 4 with step 2.
I want to write the same thing in Ruby, but the current Ruby doesn't have any notations for slice.
While I tried to use
: symbol in Ruby as Python, but it failed because
:: has the specific role.
Introducing step attribute in Range, we can get the value of step of a Range in a formal way, and we can write sliced views as following:
Updated by mrkn (Kenta Murata) about 1 year ago
- Status changed from Open to Rejected
I've discussed this issue and #13904 in today's developer meeting.
Following the discussion, I decided to withdraw the proposal of range with step.
Instead I propose to introduce a subclass of Enumerator that provides the attributes of first, last, and step values of range with step.
I will close this issue and reopen #13904 for the new proposal.