<instructions>Your goal is to analyze the following comment and estimate how highly it will be upvoted by the Hacker News community.</instructions><comment><author>anonacct37</author><text>I do like the approach of static code analysis.&lt;p&gt;I found it a little funny that their big &amp;quot;win&amp;quot; for the nilness checker was some code logging nil panics thousands of time a day. Literally an example where their checker wasn&amp;#x27;t needed because it was being logged at runtime.&lt;p&gt;It&amp;#x27;s a good idea but they need some examples where their product beats running &amp;quot;grep panic&amp;quot;.</text><parent_chain></parent_chain></comment><story><title>NilAway: Practical nil panic detection for Go</title><url>https://www.uber.com/en-NL/blog/nilaway-practical-nil-panic-detection-for-go/</url></story>
<instructions>Your goal is to analyze the following comment and estimate how highly it will be upvoted by the Hacker News community.</instructions><comment><author>carbocation</author><text>Just tried this out on some of my own code and it nails the warts that I had flagged as TODOs (and a few more...). The tool gives helpful info about the source of the nil, too. This is great.</text><parent_chain></parent_chain></comment><story><title>NilAway: Practical nil panic detection for Go</title><url>https://www.uber.com/en-NL/blog/nilaway-practical-nil-panic-detection-for-go/</url></story>