[ruby-core:84967] [Ruby trunk Feature#14382] Make public access of a private constant call const_missing

Issue #14382 has been updated by jeremyevans0 (Jeremy Evans).


Eregon (Benoit Daloze) wrote:
> Isn't Module#deprecate_constant specifically for this usage?

`Module#deprecate_constant` deprecates all usage of the constant, both public and private.  If you want to keep a constant but change the visibility from public to private, it isn't appropriate.

----------------------------------------
Feature #14382: Make public access of a private constant call const_missing
https://bugs.ruby-lang.org/issues/14382#change-69678

* Author: jeremyevans0 (Jeremy Evans)
* Status: Open
* Priority: Normal
* Assignee: 
* Target version: 
----------------------------------------
Calling `obj.foo` where `foo` is a private method of `obj` calls `method_missing`. You would expect `klass::FOO` where `FOO` is a private constant of `klass` to call `const_missing`, but currently it doesn't.  This makes a small change so that `const_missing` will be called in such cases.
    
In addition to similarity to `method_missing`, the main reason for doing this is it offers a way to deprecate public constants.  Currently, if you have a public constant and want to make it a private constant, you can't do it without breaking possible callers.  With this patch, you can make it a private constant, then override `const_missing` in the class, and have `const_missing` print a deprecation warning and then return the value of the constant.

---Files--------------------------------
0001-Make-public-access-of-a-private-constant-call-const_.patch (2.68 KB)


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

Unsubscribe: <mailto:[e-mail]?subject=unsubscribe>
<http://lists.ruby-lang.org/cgi-bin/mailman/options/ruby-core>