<p>With all data science stuff been heard everyday, i decided to make a package that's capable of analysing any type in Go. So in these 4 days i think i've made a solid base on this.</p>
<p>Pkg: <a href="https://github.com/Shixzie/analytics" rel="nofollow">https://github.com/Shixzie/analytics</a></p>
<p>This is the most complex thing i've made so far and so the first time i ever touch the reflect pkg. It still on development, but i would say it's 70%ish ready. Would like to see your opinion.</p>
<p>EDIT:</p>
<p>Now you can see the output on the README.</p>
<hr/>**评论:**<br/><br/>Astra108: <pre><p>Interesting. Always good to see more data science and analytics done in Go. </p>
<p>What is the example output? Any thoughts on incorporating graphics?</p></pre>Shixz: <pre><p>I haven't touched graphics either but it's a good idea. I'll keep working on it.</p></pre>itsmontoya: <pre><p>I took a quick glance at the analytics.go file, it looked pretty solid. I'll take a better look at it later when I'm in front of a computer.</p></pre>nathj07: <pre><p>I will also take a proper look later.</p>
<p>My first thought is that the README could do with showing the results of the example code. This may then need a little explanation too, covering what is analysed and why.</p></pre>Shixz: <pre><p>I'm aware i have to improve that README, the whole idea of the pkg is that you can give it anything and it will return a bunch of data 4 example: you give it a struct with a []string, it will return info such as "avg string length, max string length, min string length, number of words, number of unique words, number of repeated words, and so on for every type" if there's something you don't want to analyze, you can use the <code>analytics:"ignore"</code> tag as the README shows.</p></pre>Shixz: <pre><p>I've improved the README, everything is analyzed.</p></pre>