From: "Eregon (Benoit Daloze)" Date: 2022-07-20T10:54:47+00:00 Subject: [ruby-core:109259] [Ruby master Bug#18927] Can't access class variable directly with class inheritance Issue #18927 has been updated by Eregon (Benoit Daloze). mame (Yusuke Endoh) wrote in #note-2: > > It's best to avoid using class variables completely in Ruby. > > Agreed. Since we seem on the same page here, could we officially deprecate class variables? Concretely I think it should be mentioned in the documentation, and maybe also a deprecation warning? ---------------------------------------- Bug #18927: Can't access class variable directly with class inheritance https://bugs.ruby-lang.org/issues/18927#change-98390 * Author: jemmai (Jemma Issroff) * Status: Rejected * Priority: Normal * ruby -v: 3.1.2 * Backport: 2.7: UNKNOWN, 3.0: UNKNOWN, 3.1: UNKNOWN ---------------------------------------- If a child class inherits from a parent class, and the child class sets a class variable, the parent class can't access the class variable literal: ``` class Parent def self.class_var puts @@class_var end end class Child < Parent @@class_var = "class_var" end Child.class_var # => test.rb:3:in `class_var': uninitialized class variable @@class_var in Parent (NameError) ``` Confusingly, if we use `class_variable_get` (method lookup) to access `@@class_var`, we can access it as expected. We can alter the snippet from above to see this behavior: ``` class Parent def self.class_var puts class_variable_get(:@@class_var) puts @@class_var end end class Child < Parent @@class_var = "class_var" end Child.class_var # => "class_var" # => test.rb:4:in `class_var': uninitialized class variable @@class_var in Parent (NameError) ``` ## Is this desired behavior? `self` is the subclass so it seems like the class variable should be looked up on the receiver. Why is the method lookup resolution different than the literal? Should it be different? -- https://bugs.ruby-lang.org/ Unsubscribe: