From: matz@... Date: 2020-11-20T06:37:09+00:00 Subject: [ruby-core:100959] [Ruby master Bug#11022] opening an eigenclass does not change the class variable definition context Issue #11022 has been updated by matz (Yukihiro Matsumoto). Status changed from Assigned to Rejected I am not a big fan of this behavior, but I don't think class variables are worth breaking the existing code for the sake of preference. So I reject the proposal. Matz. ---------------------------------------- Bug #11022: opening an eigenclass does not change the class variable definition context https://bugs.ruby-lang.org/issues/11022#change-88616 * Author: bughit (bug hit) * Status: Rejected * Priority: Normal * Assignee: matz (Yukihiro Matsumoto) * 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: