From: zverok.offline@... Date: 2020-12-14T19:07:03+00:00 Subject: [ruby-core:101450] [Ruby master Bug#17388] Doesn't Warning.warn support `category: :experimental` in Ruby 3.0.0? Issue #17388 has been updated by zverok (Victor Shepelev). In addition: ```ruby warn('foo', category: :deprecated) # works warn('foo', category: :experimental) # ArgumentError (invalid warning category used: experimental) ``` It all comes down to this commit: https://github.com/ruby/ruby/commit/346301e2329c46362a6089311d0a64b8734b35ec Stating > The only currently defined warning category is `:deprecated`, since that is what is already used. More categories can be added in later commits. TBH, I am not sure why this method needs to use a [separate hash](https://github.com/ruby/ruby/commit/346301e2329c46362a6089311d0a64b8734b35ec#diff-f2e6c18de8171e389aeff0b8d25b2755253108a59a13baf7167c2ffa0af36a58R2797), instead of supporting all the categories `Warning[]` supports?.. @jeremyevans0, can you please explain? ---------------------------------------- Bug #17388: Doesn't Warning.warn support `category: :experimental` in Ruby 3.0.0? https://bugs.ruby-lang.org/issues/17388#change-89220 * Author: jnchito (Junichi Ito) * Status: Open * Priority: Normal * ruby -v: ruby 3.0.0preview2 (2020-12-08 master d7a16670c3) [x86_64-darwin20] * Backport: 2.5: UNKNOWN, 2.6: UNKNOWN, 2.7: UNKNOWN ---------------------------------------- I wrote the following script: ```ruby module Warning def self.warn(message, category: nil) puts "category=#{category}" super end end lambda(&:foo).lambda? Ractor.new{} ``` Then, run it: ``` $ ruby -w ~/Desktop/test.rb category=deprecated /Users/jnito/Desktop/test.rb:7: warning: lambda without a literal block is deprecated; use the proc without lambda instead category= :38: warning: Ractor is experimental, and the behavior may change in future versions of Ruby! Also there are many implementation issues. ``` I got `category=deprecated` as I expected, but got `nil` instead of `:experimental`. I feel it should be `:experimental`. This issue is related to https://bugs.ruby-lang.org/issues/17122 -- https://bugs.ruby-lang.org/ Unsubscribe: