The description of eqv was slightly outdated

Author: Jan-Olof Hendig

doc/Language/operators.pod6

@@ -1480,16 +1480,17 @@ the same, i.e. from the same type and (recursively) contain the same values.
     say 1 eqv 2;                        # False
     say 1 eqv 1.0;                      # False
 
-For arbitrary objects this is not possible with the default C<eqv> operator.
-E.g., C<eqv> will not consider two instances of the same object as being
-structurally equivalent:
+The default C<eqv> operator even works with arbitrary objects. E.g., C<eqv>
+will consider two instances of the same object as being structurally
+equivalent:
 
     my class A {
         has $.a;
     }
-    say A.new(a => 5) eqv A.new(a => 5);  #=> False
+    say A.new(a => 5) eqv A.new(a => 5);  #=> True
 
-To get C<eqv> semantics for objects of this class, one would need to
+Although the above example works as intended the C<eqv> code has to fall back
+to a slower code path in in order to do its job. One way to avoid this is to
 implement an appropriate infix C<eqv> operator:
 
     my class A {