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.

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!