[ruby-core:103072] [Ruby master Feature#17753] Add Module#outer_scope

Issue #17753 has been updated by byroot (Jean Boussier).


> Besides that, I do not see any reason to make them different in any way

Well, if `Module.nesting` because of its scope semantic can't be chained. `Module.nesting.nesting` would be problematic.

The proposed feature is very easily chainable:

```ruby
A::B::C.namespace # => A::B
A::B::C.namespace.namespace # => A
```

So returning an array doesn't give anything that's not already achievable, and cause an array allocation that some users would rather avoid in some situations.

----------------------------------------
Feature #17753: Add Module#outer_scope
https://bugs.ruby-lang.org/issues/17753#change-91134

* Author: tenderlovemaking (Aaron Patterson)
* Status: Open
* Priority: Normal
----------------------------------------
Given code like this:

```ruby
module A
  module B
    class C; end
    class D; end
  end
end
```

We can get from `C` to `B` like `C.outer_scope`, or to `A` like
`C.outer_scope.outer_scope`.

I want to use this in cases where I don't know the outer scope, but I
want to find constants that are "siblings" of a constant.  For example,
I can do `A::B::C.outer_scope.constants` to find the list of "sibling"
constants to `C`.  I want to use this feature when walking objects and
introspecting.  For example:

```ruby
ObjectSpace.each_object(Class) do |k|
  p siblings: k.outer_scope.constants
end
```

I've attached a patch that implements this feature, and there is a pull request on GitHub [here](https://github.com/ruby/ruby/pull/4326).

---Files--------------------------------
0001-Add-Module-outer_scope.patch (5.93 KB)
0001-Add-Module-namespace.patch (5.89 KB)


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

Unsubscribe: <mailto:[e-mail]?subject=unsubscribe>
<http://lists.ruby-lang.org/cgi-bin/mailman/options/ruby-core>