Show HN: LINQ for Go

The &#x27;LINQ for Go&#x27; passes around slices as sequences. It differs in both space and time complexities from the &#x27;LINQ to Objects&#x27; in C#.<p>A rather proper LINQ implementation in Go is<p><a href="http://www.oki-osk.jp/esc/golang/linq3/linq.go.html" rel="nofollow">http:&#x2F;&#x2F;www.oki-osk.jp&#x2F;esc&#x2F;golang&#x2F;linq3&#x2F;linq.go.html</a> <a href="http://www.oki-osk.jp/esc/golang/linq3/linq_test.go.html" rel="nofollow">http:&#x2F;&#x2F;www.oki-osk.jp&#x2F;esc&#x2F;golang&#x2F;linq3&#x2F;linq_test.go.html</a><p>and its design and implementation are explained in<p><a href="http://www.oki-osk.jp/esc/golang/linq3.html" rel="nofollow">http:&#x2F;&#x2F;www.oki-osk.jp&#x2F;esc&#x2F;golang&#x2F;linq3.html</a>

I&#x27;ve read many compliments about LINQ and how it was something fundamentally more powerfull than just a sql wrapper ( i think i remembered the dreaded word &quot;monad&quot;, but i&#x27;m not suree), but i haven&#x27;t found any detailled analysis of the theory behind that technology.<p>Anyone got a link to something like that ?

This looks more like a list comprehensions library for Go than a LINQ library.<p>Actual LINQ is a lot more powerful.

Didn&#x27;t explore both in depth, but at first glance I prefer the GO underscore approach: <a href="https://github.com/tobyhede/go-underscore" rel="nofollow">https:&#x2F;&#x2F;github.com&#x2F;tobyhede&#x2F;go-underscore</a>

I love everything linq. I love how I can be more expressive and do more with less. I&#x27;m assuming you&#x27;ve had exposure to C# otherwise you wouldn&#x27;t have ported the main functionality over to Go. What are your thoughts - I know that Go has its special use cases but do you find that the more &quot;verbose&quot; nature of their lamdas junk up your code? Is the extra verbosity offset by Go&#x27;s other redeeming qualities?