←back to thread

Net 9.0 LINQ Performance Improvements

(blog.ndepend.com)
201 points olvy0 | 1 comments | 18 Oct 24 10:39 UTC | HN request time: 0.204s | source
Show context
high_na_euv ◴[18 Oct 24 11:36 UTC] No.41878416[source]▶
LINQ is so fucking useful and well designed feature of .NET ecosystem that it is unreal when you gotta use lang which doesnt have such a thing.

C# design team is/was unparalleled

replies(7): >>41878459 #>>41878543 #>>41878588 #>>41878686 #>>41879163 #>>41879194 #>>41879315 #
hggigg ◴[18 Oct 24 12:16 UTC] No.41878686[source]▶
LINQ is a veritable footgun in any large team I find. While it's extremely powerful and really nice, it's so so so easy to blow your toes off if you don't know what you are doing. Some of my favourite screw ups I saw:

* Not understanding when something is evaluated.

* Not understanding the computational complexity of multiple chained operations/aggregates.

* Not understanding the expectation that Single() requires exactly one of something.

* Not understanding how damn hard it is to test LINQ stuff.

replies(5): >>41878737 #>>41878748 #>>41878838 #>>41879379 #>>41879440 #
John23832 ◴[18 Oct 24 12:36 UTC] No.41878838[source]▶
I sort of agree. I recently had to code splunk a bug with 3 other engineers and we all got to a relatively complex LINQ and of the 4 of us, we all had 4 different interpretations when visually inspecting.

> Not understanding how damn hard it is to test LINQ stuff.

I disagree with this. Just run the LINQ query on a compatible iterable.

replies(2): >>41878892 #>>41879478 #
1. hggigg ◴[18 Oct 24 12:43 UTC] No.41878892[source]▶
Regarding the testing, it's more the sheer multiplicative number of cases you have to consider on a LINQ expression.