Ad
  • Default User Avatar

    Answer to myself and maybe others:

    The tests do not want to compare the instances, as they (hopefully) are always different.
    Take care of this early and all will be fine :)

  • Default User Avatar

    Maybe this was the same error I'm running into:

    Test.assert_equals(Vector.new(1,2,3), Vector.new([1,2,3]))

    yields

    #<Vector:0x0000559eb6bc3b08 @x=1, @y=2, @z=3>, instead got: #<Vector:0x0000559eb6bc3f68 @x=1, @y=2, @z=3>

    in my implementation, although the initialization itselfs seems to do, what it is supposed to.

  • Default User Avatar

    Nvm figured it out

  • Custom User Avatar

    Without knowing what you are doing it's difficult to say what you are doing wrong :)

  • Default User Avatar

    I pass almost all the random tests but I get 14 errors. I think it all stems from the first error saying that both initializatoins should result in the same vector, what am I doing wrong? In my side IDE when I define a vector with a list, tuple, or just 3 inputs they all show the same in the IDE

  • Default User Avatar
  • Default User Avatar

    I really enjoyed this kata, it helped me learn about a few interesting methods to call on a list!
    However, it did take me two attempts because I at first was thinking it meant we were swapping any two indeces. If that's not a kata, maybe it could be a level 6!