aboutsummaryrefslogtreecommitdiffstats
path: root/activesupport/test
diff options
context:
space:
mode:
authorXavier Noria <fxn@hashref.com>2018-05-06 13:56:06 +0200
committerXavier Noria <fxn@hashref.com>2018-05-06 14:06:16 +0200
commit5c7656d9a568fda855e6e558b7e44b1ba51425be (patch)
treea2eb9e6053fa924c2a6a82d20efeb0aa4f3d8149 /activesupport/test
parent5edafc21b9e7a0fd84c5664be7c431e05c9b67fb (diff)
downloadrails-5c7656d9a568fda855e6e558b7e44b1ba51425be.tar.gz
rails-5c7656d9a568fda855e6e558b7e44b1ba51425be.tar.bz2
rails-5c7656d9a568fda855e6e558b7e44b1ba51425be.zip
restores original intention in constants guide, reworded [ci skip]
Once all technicalities have been introduced, the purpose of this paragraph is to precisely unroll expressions like "the String class". That way, the reader is forced to clearly separate concepts that Ruby programmers often have kind of blurred: * Constants are storage, like variables. * Ruby does not have syntax for class or module names. * `String` is a regular constant that holds a value. In this case, the value happens to be a class object. * Constants are stored in class and module objects. In the case of `String`, the holder is the class object stored in the `Object` constant. Understanding that paragraph the way is written is important to accomplish this objective. References #32818.
Diffstat (limited to 'activesupport/test')
0 files changed, 0 insertions, 0 deletions