←back to thread

Go is still not good

(blog.habets.se)
644 points ustad | 1 comments | 22 Aug 25 09:25 UTC | HN request time: 0.204s | source
Show context
zwnow ◴[22 Aug 25 11:48 UTC] No.44983361[source]▶
> Wait, what? Why is err reused for foo2()? Is there’s something subtle I’m not seeing? Even if we change that to :=, we’re left to wonder why err is in scope for (potentially) the rest of the function. Why? Is it read later?

First time its assigned nil, second time its overwritten in case there's an error in the 2nd function. I dont see the authors issue? Its very explicit.

replies(2): >>44983883 #>>44983884 #
1. lowmagnet ◴[22 Aug 25 12:43 UTC] No.44983884[source]▶
I'll have to read the rest later but this was an unforced error on the author's part. There is nothing unclear about that block of code. If err isn't but, it was set, and we're no longer in the function. If it's not, why waste an interface handle?