1. 4

  2. 3

    Got a nice follow-up post from the author correcting an error or two and explaining a little more.

    1. 2

      Imagine the actual interface to this problem being a person calling out “left”, “up”, “left”, etc. To run tortoise-and-hare in your head on this input, you’d have to remember what they’d called out, to an unbounded span backwards. I don’t know about ES6 iterators, but the solution seems to amount to cloning the person calling out the directions.

      1. 2

        You are absolutely correct about that, and it was no accident. I was trying to show that the Carpenter was trying to force-fit cycle-detection onto this problem, mostly because Plissken had coached him that Thing liked to test whether Candidates knew how to solve it.

        1. 1

          I see! I wondered at the time if following your blog more would have filled in some context. (I’m on a bit of an internet diet lately… relatively at least.)