News for hackers. Stuff that matters.

A comment on Analysing C# code on GitHub with BigQuery. Parent comment

Re:Analysing C# code on GitHub with BigQuery by tigershark on Friday October 13, 2017 @09:00AM (#15465170)
Why on earth? It is resolved by the compiler, there is absolutely no performance difference between using var and explicitly specifying the type.
[ Parent | on HN ]
Re:Analysing C# code on GitHub with BigQuery by ambulancechaser on Friday October 13, 2017 @10:46AM (#15466147)
undoubtedly that person was talking about LINQ and not var usage
[ Parent | on HN ]
Re:Analysing C# code on GitHub with BigQuery by tigershark on Saturday October 14, 2017 @10:21AM (#15472267)
Undoubtedly he didn't read properly then. The banned feature was var, linq was just heavily frowned upon.
[ Parent | on HN ]
Re:Analysing C# code on GitHub with BigQuery by dbattaglia on Friday October 13, 2017 @11:34AM (#15466571)
Or possibly confusing "var" and "dynamic"?
[ Parent | on HN ]
Re:Analysing C# code on GitHub with BigQuery by JustSomeNobody on Friday October 13, 2017 @11:33AM (#15466568)
Yes, LINQ not var.
[ Parent | on HN ]
Re:Analysing C# code on GitHub with BigQuery by btschaegg on Friday October 13, 2017 @01:01PM (#15467399)
Well, that on the other hand does indeed make sense, depending on the context. The only question there could be if it's a good idea to use a garbage collected language to directly[1] interact with hardware.

[1]: Well, at least directly enough for LINQ performance to be a problem.

[ Parent | on HN ]
Re:Analysing C# code on GitHub with BigQuery by JustSomeNobody on Friday October 13, 2017 @03:56PM (#15468815)
We're not real time, but we do have some time constraints.

Yes, all this was kicked around and argued about.

[ Parent | on HN ]