From: "jeremyevans0 (Jeremy Evans)" Date: 2022-06-04T01:58:30+00:00 Subject: [ruby-core:108770] [Ruby master Feature#11689] Add methods allow us to get visibility from Method and UnboundMethod object. Issue #11689 has been updated by jeremyevans0 (Jeremy Evans). matz (Yukihiro Matsumoto) wrote in #note-24: > When investigating #18435, I realized the visibility of a method is not an attribute of the method. Instead, each class should have lists of methods for each visibility. Otherwise, we would face issues like #18729 and #18751. With this understanding, Method and UnboundMethod classes should not have proposed methods. Although those methods have already been shipped with 3.1, I propose to remove the methods. I estimate the impact of removing those methods is minimal. I've submitted a pull request to revert this feature: https://github.com/ruby/ruby/pull/5974 ---------------------------------------- Feature #11689: Add methods allow us to get visibility from Method and UnboundMethod object. https://bugs.ruby-lang.org/issues/11689#change-97835 * Author: yui-knk (Kaneko Yuichiro) * Status: Closed * Priority: Normal ---------------------------------------- Add `Method#visibility` and `UnboundMethod#visibility` for getting visibility from Method and UnboundMethod object. In GitHub https://github.com/ruby/ruby/pull/1098. ---Files-------------------------------- 0001-Add-Method-visibility-and-UnboundMethod-visibility.patch (3.11 KB) -- https://bugs.ruby-lang.org/ Unsubscribe: