Issue #19600 has been updated by matz (Yukihiro Matsumoto). Status changed from Open to Closed This issue includes multiple proposals, and the rationale is only explained 'brain-friendly', which may vary person to person. Please make sure one issue contains only one proposal, with subjective rationale or real world use-cases. For this particular case, I am not convinced by any of the proposals. Matz. ---------------------------------------- Feature #19600: Method `clamp?` https://bugs.ruby-lang.org/issues/19600#change-103840 * Author: sawa (Tsuyoshi Sawada) * Status: Closed * Priority: Normal ---------------------------------------- Currently, we have pairs of non-predicate and predicate methods like `String#match` and `String#match?`. Along this line, I propose the following. They are brain-friendly, and make programmers happier by saving them from terminology hell. 1. Since by #19588, `Comparable#clamp`'s behavior is made the same as `Range#cover?` for range arguments, alias `Range#cover?` as `Range#clamp?`. 2. Synchronize the specification of `Comparable#between?` with `Comparable#clamp`, i.e., a. Allow `Comparable#between?` to take a range argument, and b. Allow `Comparable#between?` to take `nil` as either or both of its arguments, or as either or both ends of its range argument. 3. Alias `Comparable#between?` as `Comparable#clamped?` -- https://bugs.ruby-lang.org/