From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.2 (2018-09-13) on dcvr.yhbt.net X-Spam-Level: X-Spam-Status: No, score=-3.9 required=3.0 tests=AWL,BAYES_00, HEADER_FROM_DIFFERENT_DOMAINS,MAILING_LIST_MULTI,RCVD_IN_DNSWL_MED, SPF_HELO_NONE,SPF_PASS,UNPARSEABLE_RELAY shortcircuit=no autolearn=ham autolearn_force=no version=3.4.2 Received: from neon.ruby-lang.org (neon.ruby-lang.org [221.186.184.75]) by dcvr.yhbt.net (Postfix) with ESMTP id 412321F934 for ; Mon, 26 Oct 2020 07:50:56 +0000 (UTC) Received: from neon.ruby-lang.org (localhost [IPv6:::1]) by neon.ruby-lang.org (Postfix) with ESMTP id 434B9120A51; Mon, 26 Oct 2020 16:50:16 +0900 (JST) Received: from xtrwkhkc.outbound-mail.sendgrid.net (xtrwkhkc.outbound-mail.sendgrid.net [167.89.16.28]) by neon.ruby-lang.org (Postfix) with ESMTPS id 64453120A38 for ; Mon, 26 Oct 2020 16:50:14 +0900 (JST) Received: by filterdrecv-p3iad2-64988c98cc-6hl79 with SMTP id filterdrecv-p3iad2-64988c98cc-6hl79-18-5F967FDB-C 2020-10-26 07:50:51.090504007 +0000 UTC m=+212153.820882962 Received: from herokuapp.com (unknown) by geopod-ismtpd-1-8 (SG) with ESMTP id tehmMVhgRhyFHqQTuTEO3A for ; Mon, 26 Oct 2020 07:50:51.038 +0000 (UTC) Date: Mon, 26 Oct 2020 07:50:51 +0000 (UTC) From: matz@ruby.or.jp Message-ID: References: Mime-Version: 1.0 X-Redmine-MailingListIntegration-Message-Ids: 76432 X-Redmine-Project: ruby-master X-Redmine-Issue-Tracker: Feature X-Redmine-Issue-Id: 17143 X-Redmine-Issue-Author: jeremyevans0 X-Redmine-Sender: matz X-Mailer: Redmine X-Redmine-Host: bugs.ruby-lang.org X-Redmine-Site: Ruby Issue Tracking System X-Auto-Response-Suppress: All Auto-Submitted: auto-generated X-SG-EID: =?us-ascii?Q?bXEIHGfdFwsIlBTndiToCp=2Fmc2rfxRD2sZAksRKJIHU6aDXzowy+ggTvuB3xzu?= =?us-ascii?Q?bANtEtlE7EO=2FQVw7MnHzfQX9zZ45jXw=2FQtqFQvv?= =?us-ascii?Q?oSWtM4zNfVy519TbyQ+TpL61gga5AD2+Lya3dsm?= =?us-ascii?Q?kI9Z3o=2FG6ZkKUG80cFAXwbhc8DETvuR2BUN83vk?= =?us-ascii?Q?5SVxgeNrd+3ugcfgFGRogs9vGEmWqxN0Mfg=3D=3D?= To: ruby-core@ruby-lang.org X-Entity-ID: b/2+PoftWZ6GuOu3b0IycA== X-ML-Name: ruby-core X-Mail-Count: 100560 Subject: [ruby-core:100560] [Ruby master Feature#17143] Improve support for warning categories X-BeenThere: ruby-core@ruby-lang.org X-Mailman-Version: 2.1.15 Precedence: list Reply-To: Ruby developers List-Id: Ruby developers List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Errors-To: ruby-core-bounces@ruby-lang.org Sender: "ruby-core" Issue #17143 has been updated by matz (Yukihiro Matsumoto). I am OK with warning categories. But the proposed categories are too fine-grained, I think. Here's the Python warning categories: https://docs.python.org/3/library/warnings.html#warning-categories Matz. ---------------------------------------- Feature #17143: Improve support for warning categories https://bugs.ruby-lang.org/issues/17143#change-88190 * Author: jeremyevans0 (Jeremy Evans) * Status: Open * Priority: Normal ---------------------------------------- Support was recently added for Warning.warn to accept a `category` keyword. However, the initial implementation was limited to having `rb_warn_deprecated` and `rb_warn_deprecated_to_remove` use the `:deprecated` value for the `category` keyword. It doesn't make sense to me to have a `category` keyword if it is only used for deprecation, so I propose we extend the support so that `Kernel#warn` accepts a category keyword (for Ruby-level warnings) and `rb_category_warn` and `rb_category_warning` functions be added to the C-API (for C-level warnings). I also propose that we change existing `rb_warn` and `rb_warning` calls to `rb_category_warn` and `rb_category_warning`, so that all warnings issued by core Ruby are issued with an appropriate category. I have implemented support for this in a pull request: https://github.com/ruby/ruby/pull/3508 -- https://bugs.ruby-lang.org/