[ruby-core:118465] [Ruby master Feature#20609] Nested module namespace misses fallback to top level

6 Jul 2024

      Issue #20609 has been reported by abdullah.arif (Abdullah Arif).

----------------------------------------
Feature #20609: Nested module namespace misses fallback to top level
https://bugs.ruby-lang.org/issues/20609

* Author: abdullah.arif (Abdullah Arif)
* Status: Open
----------------------------------------

Currently, Ruby falls back to the top-level constants if it cannot find the Module in the local scope. This can cause it to behave unintuitively.

```ruby
module A
  module B
    MY_CONST = 'defined in A::B'
  end
end

module X
end

module X::Y
  # Ruby treats A::B the same as ::A::B, because module X::Y::A is not defined. IMO this should raise a Name error or atleast a warning.
  module A::B
    # This was meant to be scoped to X::Y::A::B'
    MY_CONST = 'defined in X::Y::A::B'
  end
  puts(::A::B::MY_CONST) # => defined in X::Y::A::B
  puts(A::B::MY_CONST) # => defined in X::Y::A::B
end

puts(X::Y::A::B::MY_CONST) # uninitialized constant X::Y::A (NameError)
```

I think Ruby should raise an error or atleast a clear warning explaining the module it is using has different nesting than what the coder might expect.

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