LINQ
Languages and libraries
collection query library
SHOW HN2014
How HN took it
2 positive, 4 neutral or asking, 0 mixed, 20 critical, out of 26 comments about the project. Thread score -0.61.
Design: 0 for, 9 againstIdea: 1 for, 5 againstPerformance: 0 for, 5 againstDocs: 1 for, 1 against
The thread, comment by comment
Each row is a top-level comment and its replies, in HN's order. Select a cell to open that comment on HN.
positive neutral or mixed critical about another commenter or something else the maker
What HN said
What people liked
Useful and interesting work, helpful to other Go developers.
From 1 comment
Sorry for my rant on the language. It's interesting what you did and definitely helpful for other people, especially if you implement the other missing parts you mentioned.
bad_user on HN
Objections
Go lacks generics, so the API needs awkward casts and function signatures.
From 4 comments
Neat. I guess Go can't do type inference on the function types though? Those anonymous function signatures are all kinds of gross.
overgard on HN> I guess Go can't do type inference on the function types though? It can't, and there are no generics which is why the input has to be cast back to a Student* in every function.…
masklinn on HNyuck, I don't understand how go people can put up without parametric polymorphism.
DanWaterworth on HNAnd the dots. Yuck.
midas007 on HN
Missing SelectMany, fold and query expression support compared to LINQ.
From 3 comments
In LINQ, the extension methods defined on IEnumerable are useful, but not that interesting, because they are standard functionality in most modern languages. I also think the…
bad_user on HN> much more interesting than Select and Where (i.e. you can implement Select and Where in terms of SelectMany). Well it doesn't provide a folding method either, and just about…
masklinn on HNSome problems with the Go implementation: Looks like go does not have something similar to extension methods, so a result() call should be put at the end to unwrap the…
olmo on HN
Goroutine-per-element approach adds heavy overhead for large inputs.
From 3 comments
From the documentation: > So if you have 1M elements as input to a plinq function, you will end up 1M goroutines. > Theoretically, there is not much wrong with that.…
krakensden on HNDoes it really sound alright to you? I mean it's not the end of the world or anything, but it's adding extra overhead which simply isn't needed when you're not gaining anything…
RyanZAG on HNJust for reference, a single goroutine has a 8 kb stack size. Having one million of these things in memory at once would require 8 Gb of memory. Obviously, the scheduler kicks…
JeanPierre on HN
Naming like Where and Select is unfortunate compared to filter and map.
From 1 comment
In LINQ, the extension methods defined on IEnumerable are useful, but not that interesting, because they are standard functionality in most modern languages. I also think the…
bad_user on HN
Requests
Add SelectMany, ToDictionary, GroupBy and Zip.
From 1 comment
I would not blame Google in particular. Go team operates like they are not part of Google most of the time. You are right about the abilities of other languages to make things…
aabalkan on HN
Support remote data sources via a pluggable query interface.
From 2 comments
Some problems with the Go implementation: Looks like go does not have something similar to extension methods, so a result() call should be put at the end to unwrap the…
olmo on HNGreat comments. I have thought about creating an interface so people can just implement their own query evaluation methods and, as you said, do querying from remote data sources.…
aabalkan on HN
Questions
How would expression trees be translated into SQL in Go?
From 1 comment
Does golang support reified code/expression trees/quoted code/whatever you wanna call it? That seems to be a rather critical part of making it work. Or you use RethinkDB's RQL…
MichaelGG on HN
Alternatives named
gen code generator for Go
From 1 comment
Another approach using code generation is gen: http://clipperhouse.github.io/gen/ (Disclaimer, I work with the guy behind it) Personally these sorts of libraries just strengthen…
kmontrose on HN
LINQ in C# and .NET
From 2 comments
The real language part of LINQ isn't the simple sequence functions (.NET had them before LINQ), it's the LINQ monad embedded into the language. While personally I don't think…
MichaelGG on HNI am afraid that's actually not 100% accurate. Microsoft also uses term "LINQ" for method-based query syntax. See here:…
aabalkan on HN