From: ko1@... Date: 2020-10-26T16:42:37+00:00 Subject: [ruby-core:100587] [Ruby master Bug#17146] Queue operations are allowed after it is frozen Issue #17146 has been updated by ko1 (Koichi Sasada). Status changed from Open to Feedback At last dev-meeting we skipped this issue because it is difficult, but no benefit to change the current behavior. BTW > AFAIK no other class undefines #freeze, that seems unfriendly. `ENV.freeze` raises an error (`freeze': cannot freeze ENV (TypeError)). ---------------------------------------- Bug #17146: Queue operations are allowed after it is frozen https://bugs.ruby-lang.org/issues/17146#change-88219 * Author: Eregon (Benoit Daloze) * Status: Feedback * Priority: Normal * ruby -v: ruby 2.6.6p146 (2020-03-31 revision 67876) [x86_64-linux] * Backport: 2.5: UNKNOWN, 2.6: UNKNOWN, 2.7: UNKNOWN ---------------------------------------- ``` [1] pry(main)> q = Queue.new => # [2] pry(main)> q.freeze => # [3] pry(main)> q << 1 => # [4] pry(main)> q.pop => 1 [5] pry(main)> q.frozen? => true ``` Found by @ko1 in https://bugs.ruby-lang.org/issues/17100#note-28 I think it's a bug, since those are clear mutations. I guess old Thread::Queue implemented in Ruby did not have this bug. -- https://bugs.ruby-lang.org/ Unsubscribe: