<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>llimllib</author><text>Presumably these are tips for coders, not for language developers. As such, the language has neither generics nor exceptions and the programmer has to deal with that.&lt;p&gt;&amp;gt; is the &amp;quot;break;&amp;quot; implicit in Go?&lt;p&gt;Yes. &lt;a href=&quot;http://golang.org/doc/effective_go.html#switch&quot; rel=&quot;nofollow&quot;&gt;http:&amp;#x2F;&amp;#x2F;golang.org&amp;#x2F;doc&amp;#x2F;effective_go.html#switch&lt;/a&gt;</text><parent_chain><item><author>joshuaellinger</author><text>Odd choice of examples...&lt;p&gt;1. The file I&amp;#x2F;O makes the case for including exceptions in the language.
Specifically, adding one-off types to deal with exceptions is a bug, not a feature.
There is a good case against exceptions but that ain&amp;#x27;t it.&lt;p&gt;2. On slide 5, it appears to show that you have to use a switch statement on a generic
to get polymorphism because the language doesn&amp;#x27;t support overloading.  Again, looks more
like a bug than a feature.&lt;p&gt;Also, is the &amp;quot;break;&amp;quot; implicit in Go?  At first glance, it looks like a coding error.</text></item></parent_chain></comment><story><title>Twelve Go Best Practices</title><url>http://talks.golang.org/2013/bestpractices.slide#1</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>bcgraham</author><text>W&amp;#x2F;r&amp;#x2F;t #2 - you&amp;#x27;re not familiar with Go but knew exactly what was going on. That&amp;#x27;s totally a feature. The language was designed around exactly that kind of reading.&lt;p&gt;&amp;quot;break;&amp;quot; is implicit in Go.</text><parent_chain><item><author>joshuaellinger</author><text>Odd choice of examples...&lt;p&gt;1. The file I&amp;#x2F;O makes the case for including exceptions in the language.
Specifically, adding one-off types to deal with exceptions is a bug, not a feature.
There is a good case against exceptions but that ain&amp;#x27;t it.&lt;p&gt;2. On slide 5, it appears to show that you have to use a switch statement on a generic
to get polymorphism because the language doesn&amp;#x27;t support overloading.  Again, looks more
like a bug than a feature.&lt;p&gt;Also, is the &amp;quot;break;&amp;quot; implicit in Go?  At first glance, it looks like a coding error.</text></item></parent_chain></comment><story><title>Twelve Go Best Practices</title><url>http://talks.golang.org/2013/bestpractices.slide#1</url></story>