From: Nobuyoshi Nakada <nobu@...>
Date: 2011-08-02T23:08:18+09:00
Subject: [ruby-core:38721] [Ruby 1.9 - Bug #5146][Closed]  Bug in Set#== on ruby 1.9.3-preview1


Issue #5146 has been updated by Nobuyoshi Nakada.

Category changed from lib to core
Status changed from Assigned to Closed
Assignee changed from Akinori MUSHA to Nobuyoshi Nakada
% Done changed from 0 to 100
ruby -v changed from - to r30514

It's a bug of Hash#hash and fixed at r32810.
----------------------------------------
Bug #5146:  Bug in Set#== on ruby 1.9.3-preview1
http://redmine.ruby-lang.org/issues/5146

Author: Bernard LAMBEAU
Status: Closed
Priority: Normal
Assignee: Nobuyoshi Nakada
Category: core
Target version: 1.9.3
ruby -v: r30514


 Hi!
 
 Sorry for reporting this bug here, but I can't log into redmine even after
 having
 requested a new password...
 
 Set#== seems buggy in ruby 1.9.3, as illustrated by the following scenario.
 I can't reproduce the bug without using Hash#delete to get another empty
 hash
 than "{ }".
 
 blambeau@kali:~/Temp$ cat test.rb
 
 require 'set'
 RUBY_VERSION
 tuple = {:hello => "world"}
 empty = tuple.dup
 empty.delete(:hello)
 puts empty == {}
 puts Set.new([{}]) == Set.new([empty])
 
 blambeau@kali:~/Temp$ ruby --version
 ruby 1.9.2p290 (2011-07-09 revision 32553) [i686-linux]
 
 blambeau@kali:~/Temp$ ruby test.rb
 true
 true
 
 [...]
 
 blambeau@kali:~/Temp$ ruby --version
 ruby 1.9.3dev (2011-07-31 revision 32789) [i686-linux]
 
 blambeau@kali:~/Temp$ ruby test.rb
 true
 false


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