From: "ioquatix (Samuel Williams) via ruby-core" Date: 2023-05-19T14:51:25+00:00 Subject: [ruby-core:113530] [Ruby master Bug#19681] The final classpath of partially named modules is sometimes inconsistent once permanently named Issue #19681 has been updated by ioquatix (Samuel Williams). Would it make sense to store insertion order or otherwise store the order (or what is an alias) so that the constant names could be resolved correctly? ---------------------------------------- Bug #19681: The final classpath of partially named modules is sometimes inconsistent once permanently named https://bugs.ruby-lang.org/issues/19681#change-103157 * Author: byroot (Jean Boussier) * Status: Open * Priority: Normal * Backport: 3.0: WONTFIX, 3.1: REQUIRED, 3.2: REQUIRED ---------------------------------------- Reported to me by @fxn ```ruby m = Module.new class m::C; end p m::C.name # => "#::C" m::D = m::C p m::D.name # => "#::C" M = m p M::C.name # => "# "#