> Yes, the Go compiler team is now working on working on fixing this issue, but defer is not a new language construct and they should have started fixing that l

> Yes, the Go compiler team is now working on working on fixing this issue, but defer is not a new language construct and they should have started fixing that long ago, considered how often it's being used. What's worse, they still didn't make it a stated goal to eliminate the overhead of using defer completely, but only talk about reducing overhead in common cases. They constantly improve defer's performance. If it's all you have against go, then I guess it's good enough for you.