Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

NilAway: Practical nil panic detection for Go

uber.com

Post reply on HN
Print view View original

261–262 of 262 posts

Re: NilAway: Practical nil panic detection for Go

#261

Post by tome »

usrbinbash wrote: post #260
tome wrote: post #259

Earlier quoted context omitted.

And to return to the topic at hand, despite that article pointing to some weakness in the Haskell community, Haskell is thriving, so "We're suggesting that people should just use Rust (or Haskell, or F#, or any other robust functional programming language) instead" seems like reasonable advice to me.

> Haskell is thriving https://news.ycombinator.com/item?id=38360177 So, according to what metric is Haskell "thriving"?

I'm not sure what you mean. Are you saying that something that occupies 0.3% of an ecosystem can't be thriving? "Thriving" is not the same concept as "widely used" or "popular"!

Re: NilAway: Practical nil panic detection for Go

#262

Post by 65a »

pjmlp wrote: post #215
65a wrote: post #172

Earlier quoted context omitted.

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…

Also possible in Go via unsafe.

Which does what it says on the tin :)
Post reply on HN