-
Dec 15th, 2014, 08:56 AM
#1
LINQ To Objects and the performance of nested “Where” calls
Ran into this article from a Reflector newsletter and thought is was worth posting here.
http://codeblog.jonskeet.uk/2014/12/08/c-6-in-action/
-
Dec 15th, 2014, 09:04 AM
#2
Re: LINQ To Objects and the performance of nested “Where” calls
Wha???
I don't see anything there about LINQ To Objects or the performance of nested “Where” calls.
Is this post automated SEO spam or something? Maybe I'm just reading-impaired.
-
Dec 15th, 2014, 09:58 AM
#3
Re: LINQ To Objects and the performance of nested “Where” calls
IT was a bad link... if you click LINQ in the tag cloud, it is then the first one listed:
http://codeblog.jonskeet.uk/2011/06/...re-quot-calls/
I suspect KEvin thought he had the url in his clipboard, but had the wrong one.
-tg
-
Dec 15th, 2014, 10:03 AM
#4
Re: LINQ To Objects and the performance of nested “Where” calls
Key line here:
Now the two will achieve the same result, and I should say up-front that in most realistic cases, it won’t make a significant difference which you use. But realistic cases aren’t nearly as interesting to investigate as pathological cases,
Problem is that a lot of people will skip over that, go straight into the meat of the article, not realizing that it's discussing a mostly theoretical case.
-tg
-
Dec 15th, 2014, 10:08 AM
#5
Re: LINQ To Objects and the performance of nested “Where” calls
Originally Posted by techgnome
IT was a bad link...
That helps, thanks. I had only tried skimming through recent posts not ones from 3 years ago.
-
Dec 15th, 2014, 10:13 AM
#6
Re: LINQ To Objects and the performance of nested “Where” calls
Hahaha! I didn't even notice the date on it.
It was just freakish luck I found it. I saw "LINQ in big letters and though, hey the post is supposed to be about LINQ, let's see... and it just happened to be the first one listed. Sheer dumb luck.
-tg
-
Dec 15th, 2014, 11:54 AM
#7
Re: LINQ To Objects and the performance of nested “Where” calls
I click on the link and get the expected page from this thread. Yes it's three years old but I see it still provoking thoughts when writing statements
-
Dec 15th, 2014, 11:56 AM
#8
Re: LINQ To Objects and the performance of nested “Where” calls
well, then you've got something stuck in your cache or something... we get a post about "C# 6 IN ACTION" which according to the link is what you've linked to:
http://codeblog.jonskeet.uk/2014/12/08/c-6-in-action/
shrug...
-tg
Posting Permissions
- You may not post new threads
- You may not post replies
- You may not post attachments
- You may not edit your posts
-
Forum Rules
|
Click Here to Expand Forum to Full Width
|