kotovalexarian-likes-github/ruby--ruby
1
0
Fork 0
mirror of https://github.com/ruby/ruby.git synced 2022-11-09 12:17:21 -05:00
Code Releases Activity

refinements.rdoc: [DOC] improved [Fix GH-1659]

Browse source 
* doc/syntax/refinements.rdocrefinements.rdoc: grammatical
  correction and code highlighting improved

* doc/syntax/refinements.rdocrefinements.rdoc: Fixnum replaced
  with Integer and Integer with Numeric

Author:    Shiva Bhusal <shivabhusal@users.noreply.github.com>

git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@59147 b2dd03c8-39d4-4d8f-98ff-823fe69b080e
This commit is contained in:
nobu 2017-06-23 00:29:45 +00:00
parent ae6ebbb3fa
commit 6dc924b606
1 changed files with 14 additions and 14 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

28
doc/syntax/refinements.rdoc
View file

@ -49,13 +49,13 @@ until the end of the current class or module definition, or until the end of
the current file if used at the top-level. the current file if used at the top-level.
You may activate refinements in a string passed to Kernel#eval. Refinements You may activate refinements in a string passed to Kernel#eval. Refinements
are active the end of the eval string. are active until the end of the eval string.
Refinements are lexical in scope. Refinements are only active within a scope Refinements are lexical in scope. Refinements are only active within a scope
after the call to using. Any code before the using statement will not have the after the call to +using+. Any code before the +using+ statement will not have the
refinement activated. refinement activated.
When control is transferred outside the scope the refinement is deactivated. When control is transferred outside the scope, the refinement is deactivated.
This means that if you require or load a file or call a method that is defined This means that if you require or load a file or call a method that is defined
outside the current scope the refinement will be deactivated: outside the current scope the refinement will be deactivated:
@ -80,7 +80,7 @@ outside the current scope the refinement will be deactivated:
x.foo # prints "C#foo in M" x.foo # prints "C#foo in M"
call_foo(x) #=> raises NoMethodError call_foo(x) #=> raises NoMethodError
If a method is defined in a scope where a refinement is active the refinement If a method is defined in a scope where a refinement is active, the refinement
will be active when the method is called. This example spans multiple files: will be active when the method is called. This example spans multiple files:
c.rb: c.rb:
@ -159,8 +159,8 @@ In a class:
end end
# not activated here # not activated here
Note that the refinements in M are not activated automatically if the class Note that the refinements in +M+ are *not* activated automatically if the class
Foo is reopened later. +Foo+ is reopened later.
In eval: In eval:
@ -180,9 +180,9 @@ When not evaluated:
end end
# not activated here # not activated here
When defining multiple refinements in the same module, inside a refine block When defining multiple refinements in the same module inside multiple +refine+ blocks,
all refinements from the same module are active when a refined method is all refinements from the same module are active when a refined method(any of the +.to_json+ method from Example below) is
called: called for the first time:
module ToJSON module ToJSON
refine Integer do refine Integer do
@ -225,12 +225,12 @@ If no method was found at any point this repeats with the superclass of +C+.
Note that methods in a subclass have priority over refinements in a Note that methods in a subclass have priority over refinements in a
superclass. For example, if the method <code>/</code> is defined in a superclass. For example, if the method <code>/</code> is defined in a
refinement for Integer <code>1 / 2</code> invokes the original Fixnum#/ refinement for Numeric <code>1 / 2</code> invokes the original Integer#/
because Fixnum is a subclass of Integer and is searched before the refinements because Integer is a subclass of Numeric and is searched before the refinements
for the superclass Integer. for the superclass Numeric. Since the method <code>/</code> is also present in child +Integer+ therefore, the method lookup never went to the superclass.
If a method +foo+ is defined on Integer in a refinement, <code>1.foo</code> However, if a method +foo+ is defined on Numeric in a refinement, <code>1.foo</code>
invokes that method since +foo+ does not exist on Fixnum. invokes that method since +foo+ does not exist on Integer.
== +super+ == +super+