Issue #20573 has been updated by tenderlovemaking (Aaron Patterson). Oops, I send this before pasting the output of the script: ``` $ ./miniruby test.rb false {"test.rb:8: warning: variable $= is no longer effective\n"=>:deprecated} ``` You can see that "deprecated" warnings are not enabled, but `Warning.warn` is still called. ---------------------------------------- Bug #20573: Warning.warn shouldn't be called for disabled warnings https://bugs.ruby-lang.org/issues/20573#change-108773 * Author: tenderlovemaking (Aaron Patterson) * Status: Open * Backport: 3.1: UNKNOWN, 3.2: UNKNOWN, 3.3: UNKNOWN ---------------------------------------- Currently `Warning.warn` will be called for all warnings, even if that particular category is disabled. For example ```ruby module Warning def warn(message, category:) p message => category end end def get_var $= end p Warning[:deprecated] get_var ``` I think that internally we should _not_ call `Warning.warn` unless the category is enabled. I've sent a PR here: https://github.com/ruby/ruby/pull/10960 -- https://bugs.ruby-lang.org/