From: knu@... Date: 2016-11-05T14:02:08+00:00 Subject: [ruby-core:77975] [Ruby trunk Bug#12198] Hash#== sometimes returns false incorrectly Issue #12198 has been updated by Akinori MUSHA. The documentation of Set clearly states the following: > * Set assumes that the identity of each element does not change > while it is stored. Modifying an element of a set will render the > set to an unreliable state. So it is not a bug, but that you are not supposed to modify an object once stored in a set. ---------------------------------------- Bug #12198: Hash#== sometimes returns false incorrectly https://bugs.ruby-lang.org/issues/12198#change-61309 * Author: Sebastian Skalacki * Status: Assigned * Priority: Normal * Assignee: Akinori MUSHA * ruby -v: ruby 2.4.0dev (2016-03-11 trunk 54086) [x86_64-darwin14] * Backport: 2.1: UNKNOWN, 2.2: UNKNOWN, 2.3: UNKNOWN ---------------------------------------- Hi! Sorry for lack of the accuracy in the bug title. I have some trouble with pinpointing the issue. According to documentation, "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 in the other hash." I was able to produce two hashes which satisfy this condition, however the method returns false. In other words, following happens: ~~~ e.class #=> Hash r.class #=> Hash e.size == r.size #=> true e.each_pair.to_a == r.each_pair.to_a #=> true e == r #=> false ~~~ That happens in Ruby 1.9.3, 2.3, 2.4 and probably in other versions as well. Pure Ruby, no gem could interfere. Happy Easter ]:-> ---Files-------------------------------- problem.rb (1.69 KB) -- https://bugs.ruby-lang.org/ Unsubscribe: