Comment on Don't unwrap options: There are better ways (2024)parentComments−jimbokun1yThe problem is the compiler doesn’t help you if you forget to check err.Although it will flag unused variable. So you will have to make an effort to deliberately ignore the error value.Still not quite as nice as the compiler forcing you to handle the error case.−int_19h1yThe problem is that idiomatic Go reuses err for multiple calls. So if you already have one call and check err after, it counts as used, and forgetting to check it on subsequent calls is not flagged.−aatd861yTrue. Not a big issue in practice and there are linters and whatnot. Variable shadowing can happen.But it's a bit orthogonal of a concern. I do have things to say about errors but my complaints are a bit more nuanced and made with hindsight.
Comments
The problem is the compiler doesn’t help you if you forget to check err.
Although it will flag unused variable. So you will have to make an effort to deliberately ignore the error value.
Still not quite as nice as the compiler forcing you to handle the error case.
The problem is that idiomatic Go reuses err for multiple calls. So if you already have one call and check err after, it counts as used, and forgetting to check it on subsequent calls is not flagged.
True. Not a big issue in practice and there are linters and whatnot. Variable shadowing can happen.
But it's a bit orthogonal of a concern. I do have things to say about errors but my complaints are a bit more nuanced and made with hindsight.