Go's infinite-stack phenomenon is completely new to me and very interesting - even if I think infinite recursion is a typical problem for any developer (not just Go). Thanks for the reference!
I'd like to add another point I stumbled across recently: slice pointer receivers. But why - slices are provided by a pointer already? Well, did you ever try to modify a slice in size, not only it's data inside a method? well, then you should be familiar with the dilemma.
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
Go's infinite-stack phenomenon is completely new to me and very interesting - even if I think infinite recursion is a typical problem for any developer (not just Go). Thanks for the reference!
I'd like to add another point I stumbled across recently: slice pointer receivers. But why - slices are provided by a pointer already? Well, did you ever try to modify a slice in size, not only it's data inside a method? well, then you should be familiar with the dilemma.