I timed out as well with this same solution. How did this one pass I wonder?

Even I'm facing the same issue with broken go tests, (11/100), (53/100), (56/100) and (77/100) numbered test are throwing very similar errors, though my code is working properly.

You're welcome! We're all in the same boat here - studying and practising.
Your solution is the most upvoted, so I chose it to leave a comment to give other people clue that there might be different, arguably more optimal approach.

Yeah You're Idea suits it better,(the idea of using a ring is just out of the box). I mean mine are you kidding it is just trash code, not fit for production - I'm learning GO .. and it's a good thing to learn from developers like you,

Thanks for the better answer I really appreciate that!

Aren't there too many memory allocations? We remove elements from the middle of the original items all the time.
IMO circular list fits better.