From: matz@...
Date: 2020-02-27T07:11:43+00:00
Subject: [ruby-core:97284] [Ruby master Feature#16644] qualified const init (self::CONST1 = 1) should be allowed in methods

Issue #16644 has been updated by matz (Yukihiro Matsumoto).


Use `const_set`. I'd rather make all const re-assignment error if compatibility does not matter.

Matz.


----------------------------------------
Feature #16644: qualified const init (self::CONST1 = 1) should be allowed in methods
https://bugs.ruby-lang.org/issues/16644#change-84401

* Author: bughit (bug hit)
* Status: Open
* Priority: Normal
----------------------------------------
```rb
module Mod1
  def self.define_consts
    const_set(:CONST1, :CONST1)

    # this is actual const re-assignment but only a warning
    const_set(:CONST1, :CONST1)
    
    
    # this is const initialization but becomes an error
    # because it looks like it could be re-assignment
    # if actual const re-assignment is only a warning
    # why is a possible const re-assignment (which might not be one), an error
    self::CONST2 = :CONST2 unless const_defined?(:CONST2, false)
    
  end
  
  define_consts
end
```



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

Unsubscribe: <mailto:ruby-core-request@ruby-lang.org?subject=unsubscribe>
<http://lists.ruby-lang.org/cgi-bin/mailman/options/ruby-core>