Hacker News new | ask | show | jobs
by tehjoker 950 days ago
speaking from personal experience, i selected go for a project because it is high perf, automatically uses all cores w/ goroutines, and is type checked
1 comments

> type checked

Kinda...

It is a type safe language, not exactly sure what you're hinting at here.
This entire post is a big workaround go's insufficient type system because nil is not modelled in it. That's not safe.
I agree I probably should have said strongly typed instead of safe, as yes, if you dereference a pointer to nil you are going to crash. That being said, I do think "possesses an untyped nil" is a pretty far cry from "not type checked at all". It's certainly much safer than languages like C or C++ which allow type punning, or Java, where both nullables and runtime exceptions associated with types are generally a more pernicious problem.
Also possible in Go via unsafe.
Which does what it says on the tin :)