[ruby-core:113646] [Ruby master Feature#19682] ability to get a reference to the "default definee"

Issue #19682 has been updated by ioquatix (Samuel Williams).


> A clear specification of what? "default definee" is quite clear in ruby internals, it has to be, there can be no ambiguity about where methods are defined. This issue is about exposing it, so what is unclear? How to expose it? "Could be a Module class method or a global method (Kernel) or a keyword."

I would suggest opening a new issue, following the feature request template, provide exact details of the interface you are proposing to introduce (e.g. `__module__` or `nesting(0)`), the scenarios where it's useful, and if it's simple enough, a PR which shows the proposed implementation. My advice is to come from the angle of "is this a useful feature?" and explaining why you think it's useful with example code or references to existing code that could be simplified with the proposed feature. If people ask questions, focus on the technical content.

> is quite clear in ruby internals, it has to be, there can be no ambiguity about where methods are defined.

While this may be true from an implementation POV, it may be accidental behaviour or underspecified/under-documented. So, I'd be extremely clear about the definition of such a feature. If you truely think this is already clearly defined in terms of CRuby, then please make a reference to the current implementation (i.e. C function).

> This issue is about exposing it, so what is unclear? How to expose it? "Could be a Module class method or a global method (Kernel) or a keyword."

Yes, it's unclear how you propose to expose it. Without example use cases, we cannot judge which approach would make the most sense, nor can we know the impact or value of the proposal.

- If you propose to introduce something which introduces a new interface, it will be more difficult to accept. e.g. `__module__`.
- If you propose a small change to an existing interface, it can be easier to accept. e.g. `nesting(n_or_range)`.

My advice is to make a specific proposal that best suits your use-case. Showing that it has a benefit to existing real-world code with real examples will help people understand your proposal. Being adversarial and confrontational with people will work against your proposal.

----------------------------------------
Feature #19682: ability to get a reference to the "default definee" 
https://bugs.ruby-lang.org/issues/19682#change-103289

* Author: bughit (bug hit)
* Status: Rejected
* Priority: Normal
----------------------------------------
https://blog.yugui.jp/entry/846

"default definee" is a pretty important context so why not make it easy to identify?

Could be a Module class method or a global method (Kernel) or a keyword.



-- 
https://bugs.ruby-lang.org/
 ______________________________________________
 ruby-core mailing list -- [e-mail]
 To unsubscribe send an email to [e-mail]
 ruby-core info -- https://ml.ruby-lang.org/mailman3/postorius/lists/ruby-core.ml.ruby-lang.org/