Fix use of coerce method

The gem's use of the #coerce method does not comport with the API as established by Ruby itself (e.g. http://ruby-doc.org/core-1.9.3/Numeric.html#method-i-coerce). This tweaks the usage of the return value to conform to the standard API.
dkubb · Feb 21, 2015 · 0f13677 · 0f13677
1 parent a6c5227
commit 0f13677
Show file tree

Hide file tree

Showing 2 changed files with 2 additions and 2 deletions.
diff --git a/lib/equalizer.rb b/lib/equalizer.rb
@@ -112,7 +112,7 @@ def eql?(other)
     #
     # @api public
     def ==(other)
-      other = coerce(other) if respond_to?(:coerce, true)
+      other = coerce(other).first if respond_to?(:coerce, true)
       other.is_a?(self.class) && cmp?(__method__, other)
     end
   end # module Methods

diff --git a/spec/unit/equalizer/methods/equality_operator_spec.rb b/spec/unit/equalizer/methods/equality_operator_spec.rb
@@ -83,7 +83,7 @@ def cmp?(comparator, other)
       # declare a private #coerce method
       described_class.class_eval do
         def coerce(other)
-          self.class.new(!!other)
+          [self.class.new(!!other), self]
         end
         private :coerce
       end