Issue #19644 has been updated by nobu (Nobuyoshi Nakada). bughit (bug hit) wrote in #note-8:
`Module.nesting(n)` does address the perf aspect, but it makes rather it too verbose and obfuscated/ugly to get the current: `Module.nesting(1)[0]`.
I thought it would be `Module.nesting(0)`, or `Module.nesting(0..)[0]`. ---------------------------------------- Feature #19644: Module::current to complement Module::nesting https://bugs.ruby-lang.org/issues/19644#change-103215 * Author: bughit (bug hit) * Status: Rejected * Priority: Normal ---------------------------------------- Module::current == Module::nesting[0] but without needlessly walking the entire nesting hierarchy. Could be useful for debugging/logging. It could also be a Kernel global (like `__method__`) or a keyword (like `__FILE__`) -- https://bugs.ruby-lang.org/