> Has anyone said the opposite? Or provided a single counter-example? Well, to start with, this issue itself. And these responses to it: https://bugs.ruby-lang.org/issues/12004#note-1 https://bugs.ruby-lang.org/issues/12004#note-...duckinator (Ellen Dash)
> The Ruby community already feels it is a safe and respectful community. The fact that this issue was raised and has continued to be discussed explicitly means that only *part* of the community feels this way. If everyone agreed, ...duckinator (Ellen Dash)
To start: I 100% agree with adding a CoC. I also agree with using the Contributor Covenant. I would be willing to consider an altered/different CoC, but not any of the ones I've seen so far. Looking at the diff that Olivier (https://b...duckinator (Ellen Dash)
Sorry that I forgot to check this again before. I've done a bit of thinking and poking around since I ran across this again today. Regarding [].rest == nil vs [].rest == []: [] is treated as a truthy value, so there if rest re...duckinator (Ellen Dash)
> @duckinator: Could you show us a real use case for Array#rest ? I'll add another update in a bit with examples. Marc-Andre: You raised some good objections. If you don't think I answer all of them let me know, because I want this a...duckinator (Ellen Dash)
Regarding Float, BigDecimal, Complex, and Rational: Agreed. Regarding `42 % 5 == 0`, I somewhat agree: it can be accomplished now, *and* it is not done often (excluding x % 2 == 0), so it may not be a good fit for core Ruby. When spli...duckinator (Ellen Dash)
I ran across this again, and decided to just implement it as `Numeric#divisible_by?`, since that makes the most sense to me. Branch on github: https://github.com/duckinator/ruby/compare/feature/numeric_divisible_by Patch: https://githu...duckinator (Ellen Dash)
And I just double-checked if those behave the same, and they do *not*: Incorrect: >> [].drop(1) => [] > ... => [] >> first => nil > ... => nil Correct: >> [][1..-1] => nil > ... => nil So it would appear there are not other choice...duckinator (Ellen Dash)
> rest = arr.drop(1) > ... Those two methods you mentioned "work," but the first isn't very clear on its intent, and the second cannot be used as a statement (which is where I have personally seen [1..-1] used the most). > See also...duckinator (Ellen Dash)
=begin I run into many instances where I end up using (({arr[1..-1]})), so I decided to add (({arr.rest})) to make that a bit less hideous. Branch on github: ((<URL:https://github.com/duckinator/ruby/compare/feature/array_rest>)) ...duckinator (Ellen Dash)
duckinator (Ellen Dash)01:41 AM Ruby Misc #12004: Code of Conduct