YARD is also broken, though I'm not sure how severe is that: https://github.com/lsegal/yard/issues/1243. I suspect this very change.skalee (Sebastian Skalacki)
# Abstract This feature request proposes introducing a new dependency constraint "!=", which will allow to blacklist a specific buggy version of some gem dependency without dropping support for older releases. # Background I am ...skalee (Sebastian Skalacki)
shan (Shannon Skipper) wrote: > That ^ pure Ruby implementation is a bit confusing and like the original one-liner it produces a lazy rather than eager enum. The reference implementation I have presented is meant to clarify what I me...skalee (Sebastian Skalacki)
I propose introducing an `Enumerator#concat(other_enum1, other_enum2, ...)` which returns an enumerator being a concatenation of `self` and passed arguments. Expectation ----------- ~~~ ruby enum1 = [1, 2, 3].each enum2 = %w[a b...skalee (Sebastian Skalacki)
I agree that `BigDecimal` output is horrible. First of all, I see no point in displaying the object's address. One rarely compares two BigDecimals by their identity. Typically `#==` or`#eql?` do matter, both are overriden and neithe...skalee (Sebastian Skalacki)
If the return value has as many items as arguments passed to the method and the items order is preserved, then the return value decomposition will be possible, for example: ~~~ruby ary = %w[c a e c] a, b, c = ary.delete("a", "b", "c...skalee (Sebastian Skalacki)
Tsuyoshi Sawada wrote: > I thought you had previously written: > ... I've reported it as an issue with `Hash#==` method initially. The lack of `Set#rehash` has been pointed out by you and I suppose it should be implemented. > Furth...skalee (Sebastian Skalacki)
IMHO documentation on Hash#== is incorrect at the moment. It says: > Equality—Two hashes are equal if they each contain the same number of keys and if each key-value pair is equal to (according to Object#==) the corresponding elements...skalee (Sebastian Skalacki)