News for hackers. Stuff that matters.

A comment on Declined Proposal: A built-in Go error check function, “try”. Parent comment

Re:Declined Proposal: A built-in Go error check function, “try” by meddlepal on Tuesday July 16, 2019 @10:16PM (#20455828)
Today I spent two hours tracking down why a nil pointer was occurring in my code. Turns out I forgot to pass it along to the struct initializer through one of the damn factory functions I need to create so I can hide internal fields properly... this was nested code in a framework.

Tell me again how easy it is to debug Go. In other languages the compiler can just tell me in _seconds_ that I done fucked up.

If you response includes "You're doing it wrong if you have deeply nested framework code" then you can rightly fuck right off too.

[ Parent | on HN ]
Re:Declined Proposal: A built-in Go error check function, “try” by sagichmal on Wednesday July 17, 2019 @12:09AM (#20456368)
Why are you using factory functions? Why are you trying to hide internal fields? The description of what you have to do is setting off some warning bells. It's certainly possible to write difficult-to-maintain code in any language.

> If you response includes "You're doing it wrong if you have deeply nested framework code" then you can rightly fuck right off too.

I mean, can you point me to an example? Absent more context, I'm pretty confident that you're indeed doing at least something wrong...

[ Parent | on HN ]
Re:Declined Proposal: A built-in Go error check function, “try” by meddlepal on Wednesday July 17, 2019 @01:16AM (#20456692)
Because we don't want to export internal fields of structures in our API or we need to perform initialization logic before considering the structure ready for use?

That's a pretty common use case but ignore that for a moment and just distill the problem down to it is possible to have null pointer issues in Go code.

Another example eith sufficient use of goroutines and channels it gets really tricky to debug something when a receiving channel blocks because something isn't sending.

There's plenty more. I don't find Go any simpler to debug than Java, Kotlin, Rust, or Python and in many cases it is significantly more difficult because you're constantly fighting the type system or working through huge amounts of boilerplate.

[ Parent | on HN ]