> Hence there is less overhead for managing stack frames. Isn't the point of saying to Go has not TCO, that this overhead is not being get rid of? So in Go the

> Hence there is less overhead for managing stack frames. Isn't the point of saying to Go has not TCO, that this overhead is not being get rid of? So in Go there should be no difference in performance because the stackframes get created even if not needed because Go can not recognize that it's not needed? Or am I mixing things up?