From: nobu@...
Date: 2020-12-15T07:32:59+00:00
Subject: [ruby-core:101463] [Ruby master Bug#17388] Doesn't Warning.warn support `category: :experimental` in Ruby 3.0.0?

Issue #17388 has been updated by nobu (Nobuyoshi Nakada).


BTW, `rb_category_warn` and `rb_category_warning` take the category as a string instead of `rb_warning_category_t`?

I was going to move it under "include/" when exposing functions that use it...

----------------------------------------
Bug #17388: Doesn't  Warning.warn support `category: :experimental` in Ruby 3.0.0?
https://bugs.ruby-lang.org/issues/17388#change-89233

* 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=
<internal:ractor>: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


---Files--------------------------------
experimental.diff (5.2 KB)


-- 
https://bugs.ruby-lang.org/

Unsubscribe: <mailto:ruby-core-request@ruby-lang.org?subject=unsubscribe>
<http://lists.ruby-lang.org/cgi-bin/mailman/options/ruby-core>