Issue #7580 has been updated by naruse (Yui NARUSE).

Status changed from Open to Assigned
Assignee set to matz (Yukihiro Matsumoto)

charliesome (Charlie Somerville) wrote:
> Do you propose that (({Range#<<})) would use (({#-})) and (({Range#>>})) would use (({#+})), or would it be a different method call internally?

Don't use +/- and use <</>> or Range#shift().

> I am happy with both alternatives, I just want nice convenience methods for this operation.

In my experience, such alternative name considered harmful
because if you want to add another method as Arange#+ in the future, those aliases prevent it.
----------------------------------------
Feature #7580: Range translation
https://bugs.ruby-lang.org/issues/7580#change-34795

Author: charliesome (Charlie Somerville)
Status: Assigned
Priority: Normal
Assignee: matz (Yukihiro Matsumoto)
Category: 
Target version: 


=begin
I would like to propose the (({#+})) and (({#-})) methods on (({Range})).

These would be useful for translating ranges - for example, given a range where the endpoints are 1-indexed, the range could be translated by 1 in the negative direction to use in (({Array#[]})).

Instead of doing a syntactically-bulky manual translation like so:

  ary[(range.begin - 1)..(range.end - 1)]

(({Range#-})) could be used instead:

  ary[range - 1]

The translation methods would not handle certain endpoint types specially, they would just pass the call on.

Here's an example implementation in Ruby:

  class Range
    def +(other)
      Range.new(self.begin + other, self.end + other, exclude_end?)
    end

    def -(other)
      Range.new(self.begin - other, self.end - other, exclude_end?)
    end
  end

=end


-- 
http://bugs.ruby-lang.org/