From: bughit.github@... Date: 2019-09-05T22:44:28+00:00 Subject: [ruby-core:94789] [Ruby master Bug#11022] opening an eigenclass does not change the class variable definition context Issue #11022 has been updated by bughit (bug hit). > I assume this is intentional behavior When you close bugs it would be nice to get something more authoritative than "I assume" ---------------------------------------- Bug #11022: opening an eigenclass does not change the class variable definition context https://bugs.ruby-lang.org/issues/11022#change-81405 * Author: bughit (bug hit) * Status: Rejected * Priority: Normal * Assignee: * Target version: * ruby -v: ruby 2.2.1p85 (2015-02-26 revision 49769) [i686-linux] * Backport: 2.0.0: UNKNOWN, 2.1: UNKNOWN, 2.2: UNKNOWN ---------------------------------------- ```ruby module Mod1 class << Object.new C = 1 @@cv = 1 p Module.nesting, constants(false), class_variables(false), Mod1.class_variables(false) end end ``` ``` [#>, Mod1] [:C] [] [:@@cv] ``` Shouldn't class var resolution be relative to the current lexical class (Module.nexting.first)? -- https://bugs.ruby-lang.org/ Unsubscribe: