Go 1.8 Release Candidate 1 is released
It would be neat if there was a Go Playground running the latest beta&#x2F;RC version of Go. (Or is there?)<p>I wanted to quickly test out the new struct type conversion behavior and obviously my code[1] doesn&#x27;t compile on the normal playground.<p>Perhaps interesting to note, the `beta.golang.org`[2] homepage specifically adds an inline `display:none` style to the div containing the mini Go Playground which is normally on the `golang.org`[3] homepage - removing that style in the Chrome inspector, you can see the mini Playground, but it doesn&#x27;t work. Upon closer inspection, the code to init the playground is still there, but the `playground.js` script isn&#x27;t – the init code, however, checks for this so it doesn&#x27;t throw any errors.<p>I like the attention to detail, at least – you don&#x27;t want the homepage for a beta version to have the plaground running the current stable release version; that would be pretty confusing. Still, I wonder why the HTML and JS initialization code for the playground is still there? If they went through the effort to add a `display:none` style to the HTML and a condition to check if the Playground script is available, why not just remove it entirely?<p>Just my random thoughts - obviously not a big deal at all, I just found it interesting!<p>[1] <a href="https:&#x2F;&#x2F;play.golang.org&#x2F;p&#x2F;_OSA3O2vTR" rel="nofollow">https:&#x2F;&#x2F;play.golang.org&#x2F;p&#x2F;_OSA3O2vTR</a><p>[2] <a href="https:&#x2F;&#x2F;beta.golang.org&#x2F;" rel="nofollow">https:&#x2F;&#x2F;beta.golang.org&#x2F;</a><p>[3] <a href="https:&#x2F;&#x2F;golang.org&#x2F;" rel="nofollow">https:&#x2F;&#x2F;golang.org&#x2F;</a>